This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: [patch/RFA] multiarch INSTRUCTION_NULLIFIED
- From: Daniel Jacobowitz <drow at false dot org>
- To: Randolph Chung <randolph at tausq dot org>
- Cc: Andrew Cagney <cagney at gnu dot org>, gdb-patches at sources dot redhat dot com
- Date: Wed, 1 Dec 2004 12:19:10 -0500
- Subject: Re: [patch/RFA] multiarch INSTRUCTION_NULLIFIED
- References: <200411181655.iAIGthDa026050@juw15.nfra.nl> <20041123174937.GL9148@tausq.org> <41AA09F8.4020006@gnu.org> <20041128184141.GG6359@tausq.org> <41AA2D08.3030304@gnu.org> <20041129033013.GJ6359@tausq.org> <41AB3C1D.80509@gnu.org> <20041201061924.GZ6359@tausq.org> <20041201171137.GA8037@nevyn.them.org> <20041201171712.GE6359@tausq.org>
On Wed, Dec 01, 2004 at 09:17:12AM -0800, Randolph Chung wrote:
> > Here's an off-the-cuff idea for you. Could you actually skip the
> > nullified instruction, if you had a hook in the right place? That is,
> > when a thread stops, if it is stopped at a nullified instruction,
> > forcibly move it to the next instruction before returning control to
> > GDB.
>
> this is exactly what the instruction_nullified method that i added do :)
Could you do this at the end of the to_wait hook, if I provided a way
for the native target to override to_wait? Oh, I guess it's an
architecture property, not a target property, so you'd need to do it
for remote stubs too.
--
Daniel Jacobowitz