[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: possibly disregard gdb output



I've been away for a week and no longer sure if this was updated. grr. i'll have to check if this is -.2 or -.2p1 now. sigh...

Rob Munsch wrote:

gdb> bt
#0 0xb7e5b941 in kill () from /lib/libc.so.6
#1 0xb7e5b6e5 in raise () from /lib/libc.so.6
#2 0xb7e5ca66 in abort () from /lib/libc.so.6
#3 0x08056651 in sigsegv_handler (signum=0x0) at sig.c:57
#4 <signal handler called>
#5 0xb7e9930c in mempcpy () from /lib/libc.so.6
#6 0xb7e905a1 in _IO_default_xsputn () from /lib/libc.so.6
#7 0xb7e6ef60 in vfprintf () from /lib/libc.so.6
#8 0xb7e876ec in vsprintf () from /lib/libc.so.6
#9 0xb7e7561d in sprintf () from /lib/libc.so.6
#10 0x08049ed0 in unix_cpu_report (hostname=0x20202020 <Address 0x20202020 out of bounds>, hinfo=0x20c7, fromline=0x303a3030 <Address 0x303a3030 out of bounds>, timestr=0x34313a31 <Address 0x34313a31 out of bounds>, uptimestr=0x736f7020 <Address 0x736f7020 out of bounds>, whostr=0x65726774 <Address 0x65726774 out of bounds>, psstr=0x73203a73 <Address 0x73203a73 out of bounds>, topstr=0x6e616863 <Address 0x6e616863 out of bounds>) at hobbitd_client.c:242
#11 0x3f203430 in ?? ()
#12 0x20202020 in ?? ()
#13 0x20202020 in ?? ()


... at this point, please not that lines #14 - #2387 (!!) all look the same as the previous three - the address varies, but it's 2300+ lines of "<address> in ??." If that whole list is somehow useful, let me know.. otherwise i'll just cut to the end:

#2384 0x20203937 in ?? ()
#2385 0x614a2030 in ?? ()
#2386 0x2034306e in ?? ()
#2387 0x2020203f in ?? ()
Cannot access memory at address 0xbfea0000
gdb>




Henrik Stoerner wrote:

On Wed, Jan 11, 2006 at 02:52:58PM -0500, Rob Munsch wrote:


ooookay (and i assume you mean the hobbitd_client service), that does indeed make it Go Away - but, if it ever crashes again for any reason, it will reappear red then go perma-purple again, requiring another manual Drop, yes?

Surely there's a better way to handle this..?


Yes there is - fix the bug that makes hobbitd_client crash, and you
won't see any hobbitd_client statuses. Ever.

For starters, check that you are running the latest version (4.1.2p1 -
the older versions do have bugs in the hobbitd_client code). And check the "Reporting Bugs" part of
http://www.hswn.dk/hobbit/help/known-issues.html



Regards, Henrik


To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe (at) hswn.dk






To unsubscribe from the hobbit list, send an e-mail to
hobbit-unsubscribe (at) hswn.dk