In message <[EMAIL PROTECTED]>, Daniel L ang writes: >Hi folks, > >before I send a PR, I though I'll ask about the opinion >of the people here. > >Background: > >We run an IRCnet ircd on a FreeBSD box here. This combination >lived very happy for a very long time. Recently I've updated >the box to 4.7-RELEASE-p2. After the update, the "ircd" >won't start any longer. > >Recompile of ircd did not help at all. > >ow, after many hours trying to debug the problem, I built >a world with CFLAGS=-g to get a libc with debugging symbols >and a useful backtrace: > >(gdb) bt >#0 0x2819244b in malloc_bytes (size=476) > at /usr/src/lib/libc/../libc/stdlib/malloc.c:673 >#1 0x28192581 in imalloc (size=476) > at /usr/src/lib/libc/../libc/stdlib/malloc.c:715 >#2 0x28192a44 in malloc (size=476) > at /usr/src/lib/libc/../libc/stdlib/malloc.c:1076 >#3 0x281885b5 in calloc (num=1, size=476) > at /usr/src/lib/libc/../libc/stdlib/calloc.c:49
I think we can more or less conclude that something has trashed your memory. I'd suggest you try to run your program with ElectricFence or similar. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
