Bug 309222 - Memory view doesn't work with DSF and GDB 7.0.1
Summary: Memory view doesn't work with DSF and GDB 7.0.1
Status: NEW
Alias: None
Product: CDT
Classification: Tools
Component: cdt-debug-dsf-gdb (show other bugs)
Version: 7.0   Edit
Hardware: PC Linux-GTK
: P3 normal with 2 votes (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact: Jonah Graham CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-04-14 16:58 EDT by James Blackburn CLA
Modified: 2020-09-04 15:24 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description James Blackburn CLA 2010-04-14 16:58:28 EDT
Debugging helloworld on linux x86_64 the memory view doesn't work correctly with GDB 7.0.1.  It does however work with 6.8, and CDI works with both.

Looking at the DSF trace, it does:

907,435 24-data-read-memory --thread 1 0 x 1 1 1176
907,436 24^error,msg="Unable to read memory."

CDI does:
96-data-read-memory 4195536 x 1 1 100
96^done,addr="0x00000000004004d0",nr-bytes="100",total-bytes="100",next-row="0x0000000000400534",prev-row="0x000000000040046c",next-page="0x0000000000400534",prev-page="0x000000000040046c",memory=[{addr="0x00000000004004d0",data=["0xc6",...]}]

Interestingly under 6.8 the main thread is shown as Thread[0], whereas 7.0.1 shows Thread[1].

In both cases I'm trying to display $pc which is 0x4004D0.  DSF seems to have attempted to display address 0. No matter how many many renderings I open (at any address), there's no more memory related output in the trace (stepping etc. works and correctly appears in the trace).