This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
gdb/110: Delete sim/SIM_HAVE_BREAKPOINTS and gdb/SIM_HAS_BREAKPOINTS.
- To: gdb-gnats at sources dot redhat dot com
- Subject: gdb/110: Delete sim/SIM_HAVE_BREAKPOINTS and gdb/SIM_HAS_BREAKPOINTS.
- From: ac131313 at cygnus dot com
- Date: 7 Jul 2001 02:38:47 -0000
- Reply-To: ac131313 at cygnus dot com
>Number: 110
>Category: gdb
>Synopsis: Delete sim/SIM_HAVE_BREAKPOINTS and gdb/SIM_HAS_BREAKPOINTS.
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: unassigned
>State: open
>Class: change-request
>Submitter-Id: net
>Arrival-Date: Fri Jul 06 19:48:01 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator: ac131313@cygnus.com
>Release: unknown-1.0
>Organization:
>Environment:
>Description:
Delete sim/SIM_HAVE_BREAKPOINTS and gdb/SIM_HAS_BREAKPOINTS.
http://sourceware.cygnus.com/ml/gdb-patches/2000-07/msg00042.html
Apart from the d30v, are there any sim/common simulators that make use
of this?
A brief summary of what happened is that sim/common/sim-break.c was
created as a good idea. It turned out a better idea was to use
SIM_SIGBREAK and have GDB pass back sim_resume (..., SIGBREAK).
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: