On Mon, Jun 12, 2000 at 09:58:44PM +0200, Manuel Bouyer wrote:
> The stack trace is strange:
> #0  0x480e454f in kill ()
> #1  0x480e3cc1 in abort ()
> #2  0x480e29b3 in _tcgetattr ()
> #3  0x480e29e4 in _tcgetattr ()
> #4  0x480e389b in _tcgetattr ()
> #5  0x480e3a88 in free ()
> #6  0x480be938 in _freeaddrinfo ()
> #7  0x804ca27 in dladdr ()
> #8  0x804aee4 in dladdr ()
> #9  0x804988d in dladdr ()
> #10 0x8049561 in free ()
> (gdb)
> 
> Looks like a recursive call to free() but it's also possible that the stack
> is corrupted. I'll recompile with '-g' and investigate.

I noticed the same too, but have not been able to reproduce it (and was
away for a day and a half this weekend). Let me know if you find
something out. If freeaddrinfo() is at fault, it is probably a bug
I introduced when making reading the exports file more AF-independent.

- Frank