This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Save the length of inserted breakpoints


> Date: Fri, 3 Mar 2006 09:11:24 -0500
> From: Daniel Jacobowitz <drow@false.org>
> Cc: Mark Kettenis <mark.kettenis@xs4all.nl>, gdb-patches@sourceware.org
> 
> That patch allows us to guess whether completely unknown code is ARM or
> Thumb.  If we are guessing based on target state and user settings,
> rather than from the symbol table as we do now, it's possible for
> the guess to change between when a breakpoint is inserted and when
> it is removed.  If that happens, we can try to remove a four byte
> breakpoint as if it were a two byte breakpoint, which will lead
> to memory corruption.

Can't this be done ion the target-dependent code?  Why do we need to
know, on the GDB application level, how many bytes did the breakpoint
instruction take?


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]