|
From: Stephane D. <ste...@ex...> - 2003-06-17 06:59:35
|
Hello all, I'm trying to use helgrind on my programs, but the first attempt gave me the following messages: ==11449== Warning: SIGSEGV not in user code; either from syscall kill() ==11449== or possible Valgrind bug. This message is only shown 3 times. ==11449== Warning: SIGSEGV not in user code; either from syscall kill() ==11449== or possible Valgrind bug. This message is only shown 3 times. ==11449== Warning: SIGSEGV not in user code; either from syscall kill() ==11449== or possible Valgrind bug. This message is only shown 3 times. The program seems to go on after these messages, but does not produce any other output nor helgrind log. I kept it running several minutes like this, and nothing happened except that the process takes 100% CPU load (about 75% system and 25% user) I'm running a Mandrake 9.1 system (kernel 2.4.21-0.13mdk, gcc 3.2.2, glibc lsb-2.3.1) Stephane |
|
From: Nicholas N. <nj...@ca...> - 2003-06-20 09:43:50
|
On 17 Jun 2003, Stephane Donze wrote: > I'm trying to use helgrind on my programs, but the first attempt gave me > the following messages: > > ==11449== Warning: SIGSEGV not in user code; either from syscall kill() > ==11449== or possible Valgrind bug. This message is only shown 3 > times. > ==11449== Warning: SIGSEGV not in user code; either from syscall kill() > ==11449== or possible Valgrind bug. This message is only shown 3 > times. > ==11449== Warning: SIGSEGV not in user code; either from syscall kill() > ==11449== or possible Valgrind bug. This message is only shown 3 > times. > > The program seems to go on after these messages, but does not produce > any other output nor helgrind log. I kept it running several minutes > like this, and nothing happened except that the process takes 100% CPU > load (about 75% system and 25% user) Helgrind has one or two problems with seg faults, unfortunately... if you could narrow down your program to a simple test case, that would be very helpful. Thanks. N |
|
From: Jeremy F. <je...@go...> - 2003-06-20 15:39:05
|
On Fri, 2003-06-20 at 02:43, Nicholas Nethercote wrote: > Helgrind has one or two problems with seg faults, unfortunately... if you > could narrow down your program to a simple test case, that would be very > helpful. This thread went off list. It turned out to be a trivial problem in Helgrind's reporting code. It had already been fixed in CVS. J |