Hi-

I inherited a project at work which uses threads.  When I run in debug
mode
under KDevelop I get a popup when I startup the program saying:

Program received signal SIG64 (Real-time event 64)

I was told this is pthread related, however I do not know how to debug
this error offhand.  Any suggestions are greatly appreciated.

Thanks

More info, I ran this straight from the command line in gdb.  Seems
that
the error keeps shifting around, everytime I stub out the area it
fails in,
it pops up elsewhere.  Ive seen this happen before in code, but I dont
remember why.

My biggest question is, what does this error mean?  Like many errors,
until you understand what something means, figuring out the solution
is nearly impossible.

Thanks,
Jeff

On Jan 29, 12:35=A0pm, Jeff <j...@rahul.net> wrote:
> Hi-
>
> I inherited a project at work which uses threads. =A0When I run in debug
> mode
> under KDevelop I get a popup when I startup the program saying:
>
> Program received signal SIG64 (Real-time event 64)
>
> I was told this is pthread related, however I do not know how to debug
> this error offhand. =A0Any suggestions are greatly appreciated.
>
> Thanks

Jeff wrote:
> More info, I ran this straight from the command line in gdb.  Seems
> that
> the error keeps shifting around, everytime I stub out the area it
> fails in,
> it pops up elsewhere.  Ive seen this happen before in code, but I dont
> remember why.
> 
> My biggest question is, what does this error mean?  Like many errors,
> until you understand what something means, figuring out the solution
> is nearly impossible.

Specifically, it means that some operation initiated by the application 
(or a library it uses) is leading to delivery of a SIGRT64 signal. 
That's a realtime signal (the standard doesn't assign specific names, 
just a numeric range from SIGRTMIN to SIGRTMAX).

This is rarely likely to be a synchronous event -- though it's possible 
for a thread to 'raise(64)' (which is probably but not necessarily the 
same as what's being labeled 'SIGRT64'), that's pretty unlikely. It's 
almost certainly an ASYNCHRONOUS notification of something else 
happening within the application or system, so it may indeed occur 
anywhere within your code.

If the debugger is configured to catch signal delivery, it'll stop when 
that happens. You can continue, either ignoring the signal or delivering 
it to the application, using specific gdb commands; or you can 
reconfigure dbg to NOT catch that signal. (The latter is perhaps the 
best strategy if you're not sure why it's happening and, at least for 
now, don't care.)

You should research your gdb help to figure out how to do all that, and 
probably discover many other interesting things you can do. (But for a 
quick hint, check out "info signal" and "help handle" first.)

> Thanks,
> Jeff
> 
> On Jan 29, 12:35 pm, Jeff <j...@rahul.net> wrote:
>> Hi-
>>
>> I inherited a project at work which uses threads.  When I run in debug
>> mode
>> under KDevelop I get a popup when I startup the program saying:
>>
>> Program received signal SIG64 (Real-time event 64)
>>
>> I was told this is pthread related, however I do not know how to debug
>> this error offhand.  Any suggestions are greatly appreciated.
>>
>> Thanks
>