On Thu, Aug 30, 2007 at 02:36:31PM +0200, Petter Reinholdtsen wrote:
> > That should probably be strlen(last)+1.
> > See if that helps,
That seems to fix the overrunning malloced area problem.
At least some (and possibly all) of the cases where it was not routing
were due to incomplete data and
I got this suggestion from upstream. Can you test and see if it help
to get rid of the valgrind errors?
[Martijn van Oosterhout]
> Ok, got something: valgrind points at sprintf and gosmore only uses
> that in one place. And that function is indeed slightly dodgy. Some
> suggestions:
>
>
> Gosmore exits after doing several (2-4) routes. script of running
> it attached.
I am unable to reproduce this. The error message indicate memory
corruption problem. Can you explain in more detail how to reproduce
the problem? Can you try to run the program under valgrind (valgrind
./gosmor
Package: gosmore
Version: 0.0.0.20070819-1
Severity: important
Gosmore exits after doing several (2-4) routes.
script of running it attached.
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing')
Architecture: i386 (i686)
Kernel
4 matches
Mail list logo
