This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
breakpoints/1601: Remote debugger should try h/w breakpoints when s/w breakpoints fail
- From: jon at beniston dot com
- To: gdb-gnats at sources dot redhat dot com
- Date: 1 Apr 2004 10:32:09 -0000
- Subject: breakpoints/1601: Remote debugger should try h/w breakpoints when s/w breakpoints fail
- Reply-to: jon at beniston dot com
>Number: 1601
>Category: breakpoints
>Synopsis: Remote debugger should try h/w breakpoints when s/w breakpoints fail
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: unassigned
>State: open
>Class: change-request
>Submitter-Id: net
>Arrival-Date: Thu Apr 01 10:38:01 UTC 2004
>Closed-Date:
>Last-Modified:
>Originator: jon@beniston.com
>Release: 6.0
>Organization:
>Environment:
Cygwin - But not platform specific.
>Description:
A lot of the breakpoint code in GDB fails to work with targets that don't have support for s/w breakpoints (i.e. ROM based targets). Although you can use hbreak, a lot of the breakpoints that GDB creates as a side-effect of some other command are always s/w breakpoints.
The patch mentioned in the fix field works around this by falling back to h/w breakpoints when s/w breakpoints fail.
>How-To-Repeat:
Try debugging a ROM based application.
>Fix:
http://sources.redhat.com/ml/gdb-patches/2004-01/msg00343.html
>Release-Note:
>Audit-Trail:
>Unformatted: