[CODE] [SYSTEM] Faulty Core Dumps and AIX

From: Robert Moon (LegalWriter@msn.com)
Date: 06/01/00

Since moving my MUD from a Linux box to an RS6000 with AIX nearly a month
ago, I have not been able to generate a proper core dump.  Upon nohup
boot-up, nohup.out produces:

./autorun[49]: 16626 IOT/Abort trap(coredump)
./autorun[49]: 22414 IOT/Abort trap(coredump)
./autorun[49]: 22510 Segmentation fault(coredump)
./autorun[49]: 22302 Segmentation fault(coredump)
./autorun[49]: 22350 Segmentation fault(coredump)

Line 49 in autorun is what starts the mud (FLAGS = -q and PORT = 4000):

  bin/circle $FLAGS $PORT >> syslog 2>&1

When trying to run gdb on the core file after a crash, the following error
message is generated:

"/home/rmoon/mud/lib/core" is not a core dump: File format not recognized

The core file, by the way, is exceedingly small:

-rw-r--r--   1 rmoon    staff      40927 May 30 21:44 core

ulimit is as follows:

core file size (blocks)  unlimited
data seg size (kbytes)   131072
file size (blocks)       1048575
max memory size (kbytes) 32768
stack size (kbytes)      131072
cpu time (seconds)       unlimited
pipe size (512 bytes)    64
open files               2000
virtual memory (kbytes)  262144

I *am* able to run the mud from within gdb using the RUN command and step
through and set breaks in order to debug.  However, core dumps are
definintely not being properly generated, and I can't maintain the MUD's
operation in gdb forever.  The MUD-friendly sysadmin of the RS6000 machine
and I have no clue why this is happening.  Any suggestions are most

ICQ:  14598527

     | Ensure that you have read the CircleMUD Mailing List FAQ:  |
     |  http://qsilver.queensu.ca/~fletchra/Circle/list-faq.html  |

This archive was generated by hypermail 2b30 : 04/10/01 PDT