| 1 |
These are corrupt databases that have been known to cause problems such as |
| 2 |
segfaults or unhandled errors on one or more MaxMind DB reader implementations. |
| 3 |
Implementations _should_ return an appropriate error or raise an exception on |
| 4 |
these databases. |
| 5 |
|
| 6 |
Databases are organized into subdirectories named after the reader |
| 7 |
implementation that exposed the issue (e.g., `libmaxminddb/`). |
| 8 |
|
| 9 |
Note: `libmaxminddb/libmaxminddb-uint64-max-epoch.mmdb` contains a valid |
| 10 |
database structure with `build_epoch` set to `UINT64_MAX`. It may not produce a |
| 11 |
reader error but can cause overflow in time type conversions. |
| 12 |
|
| 13 |
If you find a corrupt test-sized database that crashes a MMDB reader library, |
| 14 |
please feel free to add it here by creating a pull request. |