This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug tdep/11876] New: PC not decremented on cont/step after hitting breakpoint for CPU32
- From: "olaf dot brust at teradyne dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: 4 Aug 2010 08:45:27 -0000
- Subject: [Bug tdep/11876] New: PC not decremented on cont/step after hitting breakpoint for CPU32
- Reply-to: sourceware-bugzilla at sourceware dot org
Remote target is stuck during debugging calling either cont or step after
hitting a software breakpoint.
I dragged down the problem to m68k-tdep.c:m68k_gdbarch_init(). Function
call "set_gdbarch_decr_pc_after_break (gdbarch, 2);" is not performed
for 'normal' M68K processors. This doesn't allow GDB to detect a breakpoint on
the PC location. Thus it tries to continue in the middle of a 4byte opcode
(0xFFFE).
Commenting out the condition fixed it for me.
Looking at the repository, it used to be in for all kinds of M68K processors,
was removed and later returned for Coldfire and Fido. m68kbsd-tdep.c and
m68klinux-tdep.c also make this call unconditional.
Target platform is Motorola 68332 running pSOS+ as OS.
--
Summary: PC not decremented on cont/step after hitting breakpoint
for CPU32
Product: gdb
Version: 7.1
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: tdep
AssignedTo: unassigned at sourceware dot org
ReportedBy: olaf dot brust at teradyne dot com
CC: gdb-prs at sourceware dot org
GCC host triplet: i686-pc-mingw32
GCC target triplet: m68k-elf
http://sourceware.org/bugzilla/show_bug.cgi?id=11876
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.