[Qt-interest] SIGSEGV with single-line gdb backtrace

[Bill King]

Bill - thanks for the quick response.
> helgrind isn't working (according to valgrind) in my current version of 
> valgrind. memcheck reports various lost memory, but no help finding a 
> SIGSEGV. In fact, the SIGSEGV didn't even occur during any valgrind 
> sessions I just ran, but the program *did* run very very slow. Which 
> leads me to believe that the SIGSEGV is being caused by some wierd 
> thread interaction.
>
> But how to you debug *that* beast?
>
> Thanks,
> -josiah
>
>   
The dreaded heisenbugs :) Update your valgrind if possible. There's a
good chance that helgrind will catch it, now... Are you locking access
to the variables that are likely to be accessed via another thread?
Definately sounds like a race condition.

-- 
Bill King, Software Engineer
Qt Development Frameworks, Nokia Pty Ltd
Brisbane Office