Msim 64bit incorrectly handles memory breakpoints

Bug #1094908 reported by Peter Júnoš
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
msim-debugger
Confirmed
High
Unassigned

Bug Description

Memory breakpoints in 64bit environment are always set as of type "-w".

Steps, how it was done:
[msim] break 0x2000 2 r
[msim] dumpbreak
Address Mode Hits
---------- ---- --------------------
0x00002000 -w 0

Stopping on memory breakpoint fails with error messages:
"<msim> gdb: Bad file descriptor"

Changed in msim-debugger:
status: New → Confirmed
importance: Undecided → High
Revision history for this message
Peter Júnoš (petoju) wrote :

This bug is also present in MSIM mainline from bzr://d3s.mff.cuni.cz/msim/mainline

[msim] break 0x1000 10 rw
[msim] dumpbreak
[address ] [mode] [hits ]
0x0000000000001000 -w 0

Mainline MSIM also fails, when reaching breakpoint and simulation ends:
<msim> Fault: Unexpected physical memory breakpoint kind
Aborted (core dumped)

However, this bug is does not appear in MSIM stable (bzr://d3s.mff.cuni.cz/msim/stable-1.3). That version uses different commands and they work as expected:

[msim] break 0x1000 rw
[msim] bd
Address Mode Hits
---------- ---- --------------------
0x00001000 rw 0
[msim] continue

Debug: Written to address 0x1000

[msim]

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.