[asb@media.mit.edu: signal 10 crash with 1.8.0p6]

------- Start of forwarded message -------
Return-Path: nop@ccs.neu.edu
From: Amy Bruckman <asb@media.mit.edu>
To: moo-cows@the-b.org
Reply-To: moo-cows@the-b.org, asb@media.mit.edu
Subject: signal 10 crash with 1.8.0p6
Date: Fri, 23 May 97 13:56:51 -0400
X-Mts: smtp
Sender: owner-moo-cows@the-b.org
Precedence: bulk
Resent-From: clue-cows <nop@nop.com>
Errors-To: clue-cows <nop@nop.com>


[Please cc any replies directly to me; I'm on the clue-cows sublist.]

I'm running 1.8.0p6 on a Dec alpha running OSF1 V3.2 69.73.
This morning, we crashed with a 'signal 10' error.  Panic dumping
was successful.

Here's the log file info.  This looks pretty innocent to me....

May 23 11:14:29: *** PANIC: Caught signal 10
#59:eval_d, line 7:  server panic
May 23 11:15:29: ... called from #39:eval_d, line 9
May 23 11:15:29: ... called from #32:subst (this == #60), line 20
May 23 11:15:29: ... called from #32:get_topic (this == #60), line 7
May 23 11:15:29: ... called from #60:get_topic, line 2
May 23 11:15:29: ... called from #6:?* help info*rmation @help (this == #113), line 36
May 23 11:15:29: (End of traceback)
May 23 11:15:29: PANIC-DUMPING on MediaMOO.db.new.PANIC ...
May 23 11:15:29: PANIC-DUMPING: Writing 11353 objects...
May 23 11:18:40: PANIC-DUMPING: Done writing 10000 objects...
May 23 11:18:56: PANIC-DUMPING: Done writing 11353 objects...
May 23 11:18:56: PANIC-DUMPING: Writing 9540 MOO verb programs...
May 23 11:19:22: PANIC-DUMPING: Done writing 5000 verb programs...
May 23 11:19:36: PANIC-DUMPING: Done writing 9540 verb programs...
May 23 11:19:36: PANIC-DUMPING: Writing forked and suspended tasks...
May 23 11:19:37: PANIC-DUMPING: Writing list of formerly active connections...
May 23 11:19:37: PANIC-DUMPING on MediaMOO.db.new.PANIC finished

Here's the core info:

~MediaMOO/db% dbx moo core
dbx version 3.11.8
Type 'help' for help.
Core file created by program "moo"

signal IOT/Abort trap at >*[__kill, 0x3ff8010ce68]      beq     r19, 0x3ff8010ce80
(dbx) where
>  0 __kill(0x11ffff060, 0x12003bff0, 0x0, 0x0, 0x3ff800e568c) [0x3ff8010ce68]
   1 raise(0x6, 0x1426e9e70, 0x100000004, 0x14000ea70, 0x100000002) [0x3ff80121830]
   2 abort(0x7c04, 0x3ff800ed374, 0x8, 0x0, 0x0) [0x3ff8010fc80]
   3 abort_server() ["server.c":196, 0x12003bc74]
   4 panic(message = (nil)) ["server.c":224, 0x12003bdb4]
   5 panic_signal(sig = 0) ["server.c":254, 0x12003bef4]
   6 parse_list_as_program(code = (...), errors = 0x1426e9e70) ["parser.y":1211, 0x12004e5b4]
   7 call_bi_func(n = 4, arglist = (...), func_pc = '\r', progr = 12, vdata = 0x2) ["functions.c":251, 0x120026a70]


Any clues?

- -- Amy
------- End of forwarded message -------

---

• Next by Subject: [bjj@sequent.com: memleak in tasks.c]
• Prev by thread: [egoff@combase.com: #define LOG_COMMANDS]
• Next by thread: [nop@kagoona.mitre.org: Catching E_PROPNF leaks in p5/p6/r2]
• Index(es):
  • Subject
  • Thread

Home |
Subject Index |
Thread Index