Re: [Valgrind-users] SIGSEGV in helgrind

[Nicholas N. <nj...@ca...>]

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