[Top][All Lists]

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

Re: Seg Fault w/ cfenvd

From: David E. Nelson
Subject: Re: Seg Fault w/ cfenvd
Date: Fri, 14 Jan 2005 13:16:11 -0600 (CST)

Hi Eric,

No, 'bt full' didn't add anything more. I agree, the signum looks suspicious. According to the man page, it's an 'int' and 1191328 sure looks awfully big for an int.

BTW, I found a handfull of Solaris systems this AM that had cfenvd core files - all the same problem.

Also, locks.c:104 is:

snprintf(OUTPUT,CF_BUFSIZE*2,"Received signal %d (%s) while doing [%s]",signum,SIGNALS[signum],CFLOCK);

I've never used gdb before, so just for my education, did the segfault occur at '#0' or '#2' below? I take it that '??' means it couldn't find any symbol info at the memory address 0xff1b3200...correct?



On Fri, 14 Jan 2005, Eric Sorenson wrote:

On Fri, 14 Jan 2005, David E. Nelson wrote:

Core was generated by `/var/cfengine/bin/cfenvd'.
Program terminated with signal 11, Segmentation fault.
#0  0xff1b3200 in ?? ()
(gdb) file /var/cfengine/bin/cfenvd
Reading symbols from /var/cfengine/bin/cfenvd...done.
(gdb) bt
#0  0xff1b3200 in ?? ()
#1  0xff207fb4 in ?? ()
#2  0x00026254 in HandleSignal (signum=1191328) at locks.c:104

Hard to know what this was, though that 'signum' looks suspicious.

Does 'bt full' say anything more?

~~ ** ~~  If you didn't learn anything when you broke it the 1st ~~ ** ~~
                        time, then break it again.

reply via email to

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