[ale] Segfault but no dump.

[Jim]

It was a memory leak.  I finally found it.  I hate libraries that 
allocate memory and rely on you to call cleanup routines.     (grumble 
grumble)
Jim wrote:
> I'm getting a strange error when I try to examine the core file of a 
> crashed app.  Here's the output:
>
> This GDB was configured as "i386-redhat-linux-gnu"...Using host 
> libthread_db library "/lib/libthread_db.so.1".
>
> Reading symbols from shared object read from target memory...done.
> Loaded system supplied DSO at 0x24a000
> Core was generated by `/usr/local/bin/loggerd -f /etc/VA/logger.conf'.
> Program terminated with signal 11, Segmentation fault.
>
> warning: svr4_current_sos: Can't read pathname for load map: 
> Input/output error
>
> Cannot access memory at address 0xb7f79000
> #0  0x00000000 in ?? ()
>
> I'm guessing a blown stack, but that's only a guess.  Does anyone have a 
> suggestion as to how to go about tracking this one down? 
>
> What's the "Can't read pathname for load map" mean? Is that normal.  I 
> didn't generate one, however I'm using -g in the cflags.
>
> Thanks,
> Jim.
> _______________________________________________
> Ale mailing list
> Ale at ale.org
> http://www.ale.org/mailman/listinfo/ale
>
>
>
>