Mailing List Archive: [mod_backhand-users] Backhand troubles.

Per your debugging instructions here is the output
from gdb.
Note: The debugger appears to hang after starting. I
have to hit ctrl-c to get back ot a cmdline. This is
the ouput from the "where" command.
------------------------------------------------------
Program received signal SIGINT, Interrupt.
0x4014fc32 in __libc_accept () from /lib/libc.so.6
(gdb) where
#0 0x4014fc32 in __libc_accept () from /lib/libc.so.6
#1 0x8099d1e in child_main ()
#2 0x809a13c in make_child ()
#3 0x809a299 in startup_children ()
#4 0x809a8c6 in standalone_main ()
#5 0x809b053 in main ()
#6 0x400b71eb in __libc_start_main (main=0x809ad0c
<main>, argc=2,
argv=0xbffffd54, init=0x804fb68 <_init>,
fini=0x80cf02c <_fini>,
rtld_fini=0x4000a610 <_dl_fini>,
stack_end=0xbffffd4c)
at ../sysdeps/generic/libc-start.c:90
(gdb)

-------------------------------------------------------
- To answer your previous question: The servers abend
within seconds of starting.

- Why are the log entries doubled when starting
apache?
-------------------------------------------------------
[Fri Sep 22 09:57:04 2000] [notice] mod_backhand --
UnixSocketDir set to /usr/local/apache/backhand
[Fri Sep 22 09:57:04 2000] [notice] mod_backhand --
Broadcast 192.168.104.255:4445 added
[Fri Sep 22 09:57:04 2000] [notice] mod_backhand --
Multicast accept 192.168.104.0/24
[Fri Sep 22 09:57:04 2000] [warn] pid file
/usr/local/apache/logs/httpd.pid overwritten --
Unclean shutdown of
previous Apache run?
[Fri Sep 22 09:57:04 2000] [notice] mod_backhand --
UnixSocketDir set to /usr/local/apache/backhand
[Fri Sep 22 09:57:04 2000] [notice] mod_backhand --
Broadcast 192.168.104.255:4445 added
[Fri Sep 22 09:57:04 2000] [notice] mod_backhand --
Broadcast 192.168.104.255:4445 added
[Fri Sep 22 09:57:04 2000] [notice] mod_backhand --
Multicast accept 192.168.104.0/24
[Fri Sep 22 09:57:04 2000] [notice] mod_backhand --
Multicast accept 192.168.104.0/24
[Fri Sep 22 09:57:16 2000] [notice] (Type <=) = {
(null), /, (null) }
[Fri Sep 22 09:57:16 2000] [notice] Func executed for
(null) [byAge(4)] (0 -> 0)
[Fri Sep 22 09:57:16 2000] [notice] Func executed for
(null) [byRandom(NULL)] (0 -> 0)
[Fri Sep 22 09:57:16 2000] [notice] Func executed for
(null) [byLoad(NULL)] (0 -> 0)
[Fri Sep 22 09:57:16 2000] [notice] All funcs executed
-> local

------------------------------------------------------
Please let me know if there is any more info I can
provide to help in the debugging effort.

Thanks for your help
TAJ

=====
*--------------------------------------------------*
* I only do what the voices in my head tell me to!*
*--------------------------------------------------*

__________________________________________________
Do You Yahoo!?
Send instant messages & get email alerts with Yahoo! Messenger.
http://im.yahoo.com/

The debugger is hanging becuase the program is running. But, more
importantly, it is tracing the parent process and not the child. I don't
understand that. gdb needs to be attached to the mod_backhand process in
order to debug it. Also, if you hit conrtol-c, that will send a sigint to the
attached process (as you can see in your session). If you were attached to
the mod_backhand process and it segfaulted it would say "Program received
signal SIGSEGV". That is the stack trace we are looking for.

The gdb man page says that "set follow-fork-mode child" will tell gdb to
follow children after forking instead of staying with the parent. "set
follow-fork-mode parent" is the default.

I am stumped. Without hacking it on it myself, I don't know what could be
wrong.

Anyone else have any ideas?

terry jones wrote:
> have to hit ctrl-c to get back ot a cmdline. This is
> the ouput from the "where" command.
> ------------------------------------------------------
> Program received signal SIGINT, Interrupt.
> 0x4014fc32 in __libc_accept () from /lib/libc.so.6

--
Theo Schlossnagle
1024D/A8EBCF8F/13BD 8C08 6BE2 629A 527E 2DC2 72C2 AD05 A8EB CF8F
2047R/33131B65/71 F7 95 64 49 76 5D BA 3D 90 B9 9F BE 27 24 E7