[OSM-talk] Is gosmore broken with the latest planet file?
Petter Reinholdtsen
pere at hungry.com
Sun Aug 5 00:01:51 BST 2007
Is gosmore broken? It crashes when I try to load the latest planet
file. It work with an older file (planet-061227.osm.bz2).
This is the error message and how it crashes (gdb backtrace):
*** glibc detected *** double free or corruption (out): 0xa9002008 ***
Program received signal SIGABRT, Aborted.
[Switching to Thread -1218394432 (LWP 9651)]
0xb7fdc410 in ?? ()
(gdb) bt
#0 0xb7fdc410 in ?? ()
#1 0xbfc5abbc in ?? ()
#2 0x00000006 in ?? ()
#3 0x000025b3 in ?? ()
#4 0xb7747811 in raise () from /lib/tls/i686/cmov/libc.so.6
#5 0xb7748fb9 in abort () from /lib/tls/i686/cmov/libc.so.6
#6 0xb777cd3a in __fsetlocking () from /lib/tls/i686/cmov/libc.so.6
#7 0xb77845cf in mallopt () from /lib/tls/i686/cmov/libc.so.6
#8 0xb7784672 in free () from /lib/tls/i686/cmov/libc.so.6
#9 0x0804de87 in main (argc=2, argv=0xbfc5b4c4) at gosmore.cc:1035
(gdb)
Any idea how to fix it?
BTW: I just uploaded a Debian package of gosmore based on the gosmore
code in subversion to Debian. I expect it to show up in the
archive within the month.
Happy hacking,
--
Petter Reinholdtsen
More information about the talk
mailing list