[1310] in Moira
Re: ttsp's moirad dies
daemon@ATHENA.MIT.EDU (K. Ramm)
Sun Jan 30 17:12:00 2000
To: moiradev@MIT.EDU
Cc: moira-admin@MIT.EDU, Garry Zacheiss <zacheiss@MIT.EDU>
From: kcr@MIT.EDU (K. Ramm)
Date: 30 Jan 2000 17:11:51 -0500
In-Reply-To: Garry Zacheiss's message of "Sat, 29 Jan 2000 20:00:12 -0500"
Message-ID: <uus4sbvdxaw.fsf@EMACS-MAKES-A-COMPUTER-SLOW.MIT.EDU>
Garry Zacheiss <zacheiss@MIT.EDU> writes:
> definitely as a result of mistere's testing client. I've
> restarted it and left a coredump in ttsp:/moira/core.012900.
>
> Garry
Bizzare; gdb thinks it died on a signal 9, which doesn't explain why it
dumped core at all, and I can't imagine why it would've died on that line
without either some one killing it or particularly nasty stack corruption.
[not that we can rule out particularly nasty stack corruption].
this-too-shall-pass.mit.edu# gdb /moira/bin/moirad /moira/core.012900
GNU gdb 4.18
...
Core was generated by `moirad'.
Program terminated with signal 9, Killed.
Reading symbols from
/u1/oracle/app/oracle/product/7.3.4/lib/libclntsh.so.1.0...done.
Reading symbols from /usr/lib/libsocket.so.1...done.
...
Reading symbols from /usr/lib/nss_dns.so.1...done.
---Type <return> to continue, or q <return> to quit---
#0 0x463c0 in mr_cont_receive (fd=11, reply=0xc9254) at mr_call.c:183
183 return MR_INTERNAL;
(gdb) where
#0 0x463c0 in mr_cont_receive (fd=11, reply=0xc9254) at mr_call.c:183
#1 0x1c580 in client_read (cl=0xc91a0) at mr_scall.c:64
#2 0x1b484 in main (argc=1, argv=0xeffffcac) at mr_main.c:316
(gdb)
