Project Home
Project Home
Trackers
Trackers
Documents
Documents
Wiki
Wiki
Discussion Forums
Discussions
Project Information
Project Info
BroadcastCommunity.qnx.com will be offline from May 31 6:00pm until June 2 12:00AM for upcoming system upgrades. For more information please go to https://community.qnx.com/sf/discussion/do/listPosts/projects.bazaar/discussion.bazaar.topc28418
Forum Topic - Problem debugging core dump: (4 Items)
   
Problem debugging core dump  
4.7.1 (with 6.4.1 tools)

I load a core dumpe file. It has 4 thread and the first one did the SIGSEGV.  But in the debug view I cannot see thread 
1.  Only the 3 other thread.

If I go in the debugger console I can type command, such as thread 1 and look for the info I want, so it's there alright
.

I setup the gdb console in verbose mode and noticed the following output

13 info tidinfo
&"info tidinfo\n"
~"Threads for pid 1834197100 (D:\\ide-4.8.0-workspace\\logc\\scanners\\depro_lc\\obj6\\depro_lc.exe)\nTid:\tState:\
tFlags:\n"
~" 4\t4\t1\n"
~" 3\t4\t1\n"
~"*2\t4\t1\n"
~" 1\t0\t129\n"

I find it suspicious that thread 1 is the one with a state and flags diffierent then the other 3.

This is happening on every core dump I check ( they all have threads )

Thanks

Re: Problem debugging core dump  
Do you know if thread 1 is, maybe detached?
If so, has it already exited (but hasn't been joined yet?)
Also what does coreinfo say?


----- Original Message -----
From: Mario Charest [mailto:community-noreply@qnx.com]
Sent: Friday, October 22, 2010 07:07 PM
To: general-ide <post72113@community.qnx.com>
Subject: Problem debugging core dump

4.7.1 (with 6.4.1 tools)

I load a core dumpe file. It has 4 thread and the first one did the SIGSEGV.  But in the debug view I cannot see thread 
1.  Only the 3 other thread.

If I go in the debugger console I can type command, such as thread 1 and look for the info I want, so it's there alright
.

I setup the gdb console in verbose mode and noticed the following output

13 info tidinfo
&"info tidinfo\n"
~"Threads for pid 1834197100 (D:\\ide-4.8.0-workspace\\logc\\scanners\\depro_lc\\obj6\\depro_lc.exe)\nTid:\tState:\
tFlags:\n"
~" 4\t4\t1\n"
~" 3\t4\t1\n"
~"*2\t4\t1\n"
~" 1\t0\t129\n"

I find it suspicious that thread 1 is the one with a state and flags diffierent then the other 3.

This is happening on every core dump I check ( they all have threads )

Thanks





_______________________________________________

General
http://community.qnx.com/sf/go/post72113
Re: Problem debugging core dump  
That means thread has exited and dead threads are not shown in IDE. The 
question is why debugger shows it as dead if you say this is the thread 
that got SIGSEGV

On 22/10/2010 7:07 PM, Mario Charest wrote:
> 4.7.1 (with 6.4.1 tools)
>
> I load a core dumpe file. It has 4 thread and the first one did the SIGSEGV.  But in the debug view I cannot see 
thread 1.  Only the 3 other thread.
>
> If I go in the debugger console I can type command, such as thread 1 and look for the info I want, so it's there 
alright.
>
> I setup the gdb console in verbose mode and noticed the following output
>
> 13 info tidinfo
> &"info tidinfo\n"
> ~"Threads for pid 1834197100 (D:\\ide-4.8.0-workspace\\logc\\scanners\\depro_lc\\obj6\\depro_lc.exe)\nTid:\tState:\
tFlags:\n"
> ~" 4\t4\t1\n"
> ~" 3\t4\t1\n"
> ~"*2\t4\t1\n"
> ~" 1\t0\t129\n"
>
> I find it suspicious that thread 1 is the one with a state and flags diffierent then the other 3.
>
> This is happening on every core dump I check ( they all have threads )
>
> Thanks
>
>
>
>
>
> _______________________________________________
>
> General
> http://community.qnx.com/sf/go/post72113
>
>    
Re: Problem debugging core dump  
I ran into the same problem with IDE 4.7.0 and QNX 6.5.0 (x86).

I contacted support and a bug report has now been filed as PR 92167.