[OSM-talk] gosmore crashes after a few searches
pere at hungry.com
Thu Aug 30 09:48:58 BST 2007
[Martijn van Oosterhout]
> Ask the bug reporter, but if you use the program yourself you can do
> it also. It slows the program a bit, but with a bit of perserverence
> you can hopefully get results.
Now the valgrind output is available from
<URL:http://bugs.debian.org/439732>, and gosmore seem to write past
allocated memory, and I suspect that mess seriously with the control
structure used by malloc() and friends.
I am unable to reproduce this problem myself, so I do not know what
more to provide to help debugging the problem.
More information about the talk