[Top][All Lists]

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

segmentation fault in InitializeLocks

From: Lars Damerow
Subject: segmentation fault in InitializeLocks
Date: Wed, 19 Jan 2005 15:11:45 -0800
User-agent: Mutt/1.5.6i

Hi folks,

Under certain circumstances (*ahem* kickstart again) cfagent dumps core with
the following gdb backtrace:

#0  0x4027d6cd in malloc_consolidate () from /lib/tls/
#1  0x4027ccaa in _int_malloc () from /lib/tls/
#2  0x4027c09d in malloc () from /lib/tls/
#3  0x400ce328 in __os_malloc () from /lib/tls/
#4  0x400ce246 in __os_calloc () from /lib/tls/
#5  0x4009cf2a in db_create () from /lib/tls/
#6  0x08085216 in InitializeLocks () at locks.c:139
#7  0x08085c49 in PutLock (name=0x40334780 "\001") at locks.c:500
#8  0x0808574c in ReleaseCurrentLock () at locks.c:346
#9  0x080519b7 in Scripts () at do.c:1419
#10 0x0804d419 in DoTree (passes=2, info=0x809a70f "Main Tree")
    at cfagent.c:1210
#11 0x0804b1ac in main (argc=10, argv=0xbffffaa4) at cfagent.c:178
#12 0x40230ad4 in __libc_start_main () from /lib/tls/
#13 0x0804afc1 in _start()

Our kickstart script invokes cfagent five or six times, and it only causes a
segmentation fault on the first invocation. It also only happens on a certain
type of machine (an IBM BladeCenter blade).

Does this look familiar to anyone, and is there any other information I can
give that might help track it down?


lars damerow
button pusher
pixar animation studios

"What makes you think tearing my head off would kill me?"    Captain Bo-Tard

reply via email to

[Prev in Thread] Current Thread [Next in Thread]