Bug 388442 - [debug view] Stacktrace length and copy stack does not work as expected
Summary: [debug view] Stacktrace length and copy stack does not work as expected
Status: NEW
Alias: None
Product: CDT
Classification: Tools
Component: cdt-debug-dsf-gdb (show other bugs)
Version: 8.1.0   Edit
Hardware: PC Windows Vista
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact: Jonah Graham CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-08-30 10:42 EDT by Mekk Elek CLA
Modified: 2020-09-04 15:26 EDT (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Mekk Elek CLA 2012-08-30 10:42:24 EDT 
When analyzing a core file in CDT, it shows the stack frames of threads.

However, the stack trace length (i.e. number of elements shown) is not taken from GDB, causing longer stacks to be truncated. Then, user has to manually click on "expand more" to see the full stack frames. There should be a configurable length in CDT itself, similar to GDB's length variable.

Another issue, related to this one is that even if all frames are expanded, the "Copy Stack" action via right click does not copy all stack frames, it is copied truncated. This means it is out of sync with the GUI.

I'm using CDT 8.1.0 on Eclipse Juno.
Comment 1 Pawel Piech CLA 2012-08-30 10:50:44 EDT 
You can configure the number of frames retrieved through a preferences: Run/Debug->View Performance->"Limit number of stack frames".

The copy problem is interesting though.  I'll investigate.  Thanks!