This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
SOFTWARE_SINGLE_STEP_P and multi-arch
- To: GDB Discussion <gdb at sourceware dot cygnus dot com>
- Subject: SOFTWARE_SINGLE_STEP_P and multi-arch
- From: Andrew Cagney <ac131313 at cygnus dot com>
- Date: Tue, 05 Dec 2000 12:13:37 +1100
Hello,
At present there are two macros that control software stepping:
SOFTWARE_SINGLE_STEP_P()
and SOFTWARE_SINGLE_STEP(sig, insert_or_remove)
I'd like to suggest the following:
Rename SOFTWARE_SINGLE_STEP_P() to TARGET_SOFTWARE_SINGLE_STEP_P() and
add it to the *target* vector.
Hardware single step support (implied
by !TARGET_SOFTWARE_SINGLE_STEP_P())
is target and not ISA/ABI dependant.
Some ISAs might support hardware single
step but the actual target may not
(lousy OS support, limited stub functionality)
Make SOFTWARE_SINGLE_STEP Multi arch.
(and I don't like it but I can't think
of a better incremental move :-)
While I think SOFTWARE_SINGLE_STEP()
should be replaced by code that creates
temp breakpoints and adds them to
the breakpoint database (gdb would
later pull them directly) I don't want
to try and also do that.
The way software single step is
currently implemented is just ulgh...
Thoughts/comments?
Andrew