Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] Debug view does not show stack information for thread

I do see the gdb trace contain the stack frame information for that thread, and the stack frame contains 10 level depth. Below show my output, I trimmed the long listing of stack frame information but they are there.

047,108 (gdb) 

047,119 50-stack-list-frames --thread 2

047,120 51-stack-info-depth --thread 2 11

047,146 50^done,stack=[frame={level="0",addr="0x01762c40",func="MsgSend",from="/Applications/\



047,147 (gdb) 

047,147 51^done,depth="10"

047,147 (gdb) 

Clicking the "Refresh" button in the debug view toolbar does not solve the problem. Manually typing "bt" command in the gdb console solves the problem and the debug view shows the stack frame for that thread.


From: cdt-dev-bounces@xxxxxxxxxxx [cdt-dev-bounces@xxxxxxxxxxx] on behalf of Marc-Andre Laperle [malaperle@xxxxxxxxx]
Sent: Wednesday, July 17, 2013 12:03 AM
To: CDT General developers list.
Subject: Re: [cdt-dev] Debug view does not show stack information for thread

Hi Andy,

I'm assuming the gdb trace does contain the stack frames? Like
-stack-list-frames --thread 1
^done,stack=[frame={level="0",addr="0x004013c6",func="main",file="..\\src\\testGdb.cpp", ....
etc and other frames as well. Or is it showing empty information for the other frames?

That's just the very first thing I would check but I'm not a debug/gdb expert :)


On 7/16/2013 3:38 PM, Andy Jin wrote:
We have seen this problem for some times. When debug hits a break point, some threads how empty information for the stack trace. Ok, it is not completely empty, it shows the first entry and the icons below it, but the trace has no information.

Sometimes when I terminate the debug session and relaunch it, I can see the correct trace for the same thread.

I have attached a screenshot to show the problem.

Is it just a UI refresh issue?


cdt-dev mailing list

Back to the top