[hobbit] hobbitd_channel still crashing everyday
Sean R. Clark
sclark at nyroc.rr.com
Thu Oct 25 17:42:19 CEST 2007
Ahh you are correct, my binary + source did not match
Here is the stack trace from the (correct) binary (it's still crashing)
All of them all show
program terminated by signal ABRT (Abort)
0xfee60717: __lwp_kill+0x0007: jae __lwp_kill+0x15 [
0xfee60725, .+0xe ]
Current function is sigsegv_handler
58 abort();
(dbx) where
[1] __lwp_kill(0x1, 0x6), at 0xfee60717
[2] _thr_kill(0x1, 0x6), at 0xfee5ded4
[3] raise(0x6), at 0xfee0ced3
[4] abort(0x8071c20, 0x0, 0x8046758, 0xfee4dd4f, 0x8046758, 0xfee4dd4f),
at 0xfedf0969
=>[5] sigsegv_handler(signum = 11), line 58 in "sig.c"
[6] __sighndlr(0xb, 0x0, 0x80467f0, 0x80581d0), at 0xfee5fadf
[7] call_user_handler(0xb, 0x0, 0x80467f0), at 0xfee560d3
[8] sigacthandler(0xb, 0x0, 0x80467f0, 0xf, 0x0, 0x0), at 0xfee56253
---- called from signal handler with signal 11 (SIGSEGV) ------
[9] main(argc = 4, argv = 0x8046b28), line 678 in "hobbitd_channel.c"
>From this:
/*
* Try to fork a child to send in an alarm message.
* If the fork fails, then just attempt to exec() the BB command
*/
Do you have any commands I can run in gdb or dbx to help further?
The name & inbuf are not defined when I try it with the correct binary +
core
-----Original Message-----
From: Henrik Stoerner [mailto:henrik at hswn.dk]
Sent: Thursday, October 25, 2007 4:16 AM
To: hobbit at hswn.dk
Subject: Re: [hobbit] hobbitd_channel still crashing everyday
On Wed, Oct 24, 2007 at 11:05:16AM -0400, Sean R. Clark wrote:
> [8] sigacthandler(0xb, 0x0, 0x80467f0, 0xf, 0x0, 0x0), at 0xfee56253
> ---- called from signal handler with signal 11 (SIGSEGV) ------
> =>[9] bbh_item(hostin = 0x80739a8, item = BBH_NET), line 466 in
> "loadhosts.c"
> [10] load_hostnames(bbhostsfn = (nil), extrainclude = 0x8046ddc
> "hobbitd_channel", fqdn = 134508012), line 112 in "loadhosts_file.c"
This trace doesn't make sense - the "bbh_item()" function isn't called from
the "load_hostnames()" function. So I think there's some corruption of the
stack involved.
Either that, or the binary you're running doesn't match the source code you
have (ie. your source files were not used to compile the binary that is
running).
If you load the binary and core into gdb as you did to get the stack trace,
could you then do this:
gdb> fr 10
This should print out that you're now at stackframe #10, which is the
"load_hostnames" routine.
gdb> p *inbuf
gdb> p name
gdb> p title
These print out the value of a number of variables.
gdb> fr 9
gdb> p *hostin
Regards,
Henrik
To unsubscribe from the hobbit list, send an e-mail to
hobbit-unsubscribe at hswn.dk
More information about the Xymon
mailing list