[OSM-talk] gosmore crashes after a few searches

Petter Reinholdtsen pere at hungry.com
Wed Aug 29 10:29:32 BST 2007

[Martijn van Oosterhout]
> Looks like memory corruption. I'd say run it under some memory
> checking program (like valigrind) and see how it fares. Memory
> corruption generally causes the program to die far away from the
> actual error :(

Yeah, valgrind is very nice.

Are anyone here able to reproduce the problem?  I am not.  I tried
with and without valgrind myself.  From valgrind I only saw errors
related to uninitialized bytes for memory allocated within gtk
functions (Xlib related).

> 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.

Will do. :)

Happy hacking,
Petter Reinholdtsen

More information about the talk mailing list