This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
gdb/368: Infinite nr of hardware breakpoints
- From: ac131313 at redhat dot com
- To: gdb-gnats at sources dot redhat dot com
- Date: 20 Feb 2002 16:24:36 -0000
- Subject: gdb/368: Infinite nr of hardware breakpoints
- Reply-to: ac131313 at redhat dot com
>Number: 368
>Category: gdb
>Synopsis: Infinite nr of hardware breakpoints
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: change-request
>Submitter-Id: net
>Arrival-Date: Wed Feb 20 08:28:01 PST 2002
>Closed-Date:
>Last-Modified:
>Originator: ac131313@redhat.com
>Release: unknown-1.0
>Organization:
>Environment:
>Description:
A software breakpoint involves modifying target memory.
A hardware breakpoint uses a mechanism outside of the targets normal executioin environment (correct word?) and hence does not directly affect the targets execution.
Simulator targets are capable of supporting an infinite number of hardware breakpoints.
GDB's breakpoint model assumes that software breakpoints (modify memory) are cheap and plentiful why hardware breakpoints are scarce. Consequently the user has explicit control over which breakpoints use hardware (hbreak).
Mechanisms for getting GDB to use hardware breakpoints in preference to software breakpoints would be useful. Perhaphs detect this in the target, perhaphs a command to override the existing behavour.
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: