improper handling of dlpened's C++/atexit() code?

m m needacoder at gmail.com
Thu May 11 18:24:34 PDT 2006


 I am writing in regard to PR at
http://www.freebsd.org/cgi/query-pr.cgi?pr=bin%2F59552 .  I am experiencing
behavior on 6.1-PRERELEASE FreeBSD 6.1-PRERELEASE #11: Sun Mar 26 00:03:52
EST 2006 which looks a lot like something that would be caused by this PR.
This happens when apache-1.3 processes that run with Mason code receive a
SIGUSR1 (when newsyslog does log rotation) and apache gracefully kills off
all processes when restarting.  The following is the stack trace that lead
me to this PR:

> #0  0x00000000 in ?? ()
> #1  0x2949dad8 in ?? ()
> #2  0x294a02c4 in ?? ()
> #3  0x281ca708 in ?? () from /lib/libc.so.6
> #4  0xbfbfe708 in ?? ()
> #5  0x28196556 in endhostent () from /lib/libc.so.6
> #6  0x2949ed4c in ?? ()
> #7  0x280a9980 in ?? () from /libexec/ld-elf.so.1
> #8  0x280a9878 in ?? () from /libexec/ld-elf.so.1
> #9  0xbfbfe718 in ?? ()
> #10 0x2808d5ef in find_symdef () from /libexec/ld- elf.so.1
> #11 0x2808da7c in find_symdef () from /libexec/ld-elf.so.1
> #12 0x281ba09a in __cxa_finalize () from /lib/libc.so.6
> #13 0x281b9d9a in exit () from /lib/libc.so.6
> #14 0x0805cd5b in clean_child_exit (code=692716228) at http_main.c:522
> #15 0x0805e707 in just_die (sig=30) at http_main.c:3202
> #16 0x0805e72a in usr1_handler (sig=692716228) at http_main.c:3212
> #17 0xbfbfffb4 in ?? ()
> #18 0x0000001e in ?? ()
> #19 0x00000000 in ?? ()
> #20 0xbfbfe7e0 in ?? ()
> #21 0x00000002 in ?? ()
> #22 0x0805e710 in just_die () at http_main.c:3202
> #23 0x0805fdae in child_main (child_num_arg=692716228) at http_main.c:4571
> #24 0x0806046e in make_child (s=0x294a02c4, slot=0, now=0) at
> http_main.c:5051
> #25 0x080604f8 in startup_children (number_to_start=5) at http_main.c:5078
> #26 0x08060b11 in standalone_main (argc=2, argv=0xbfbfeca0) at
> http_main.c:5410
> #27 0x08061392 in main (argc=2, argv=0xbfbfeca0) at http_main.c:5767

Please let me know if you have any thoughts on the subject or if this is
completely unrelated problem.  Thanks!


More information about the freebsd-stable mailing list