[Tile-serving] [openstreetmap/osm2pgsql] Large object id triggers segfault (#965)

[mmd]

While debugging some other issue, I noticed that particularly large object ids trigger a segfault in `node_ram_cache::set_dense(long, osmium::Location const&)` at node-ram-cache.cpp:141 (tested on 8d9087f1111f4a062158e8e6b10bfbceed90899b ). I'd rather expect an error message here stating that the object id is too large.

This is not really urgent in any way, as it might only affect people mixing OSM with some other data. I thought I'd raise it anyway, as segfaults are generally not so nice.

Test example: (`osm2pgsql -d osm  tesfile.osm`).

```
<?xml version='1.0' encoding='UTF-8'?>
<osm version='0.6' generator='JOSM'>
  <node id='540000000001' timestamp='2015-01-01T00:00:00Z' uid='1' user='3' version='1' changeset='10' lat='50' lon='7'/>
</osm>
```





-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/osm2pgsql/issues/965
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tile-serving/attachments/20191029/172e6125/attachment.html>