This is the mail archive of the 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: [RFA] Displaced stepping just enable in non-stop mode

P record can support displaced stepping but it don't support non-step.
 So we remove this code.

On Fri, Oct 17, 2008 at 22:48, Pedro Alves <> wrote:
> On Thursday 16 October 2008 22:15:30, Michael Snyder wrote:
>> What it looks like is that you try to write to memory
>> that's write-protected.
>> This is because most replay targets will treat all of memory
>> as write-protected when they are in replay mode.
>> Where this usually manifests is, you'll say "continue"
>> (probably for the first time since attaching to the target),
>> and it'll croak because it's trying to step over some
>> "invisible" breakpoint such as the one that handles
>> shared libraries.
> I see, then this means that all the reverse targets in existance
> implement inserting breakpoints (target_insert_breakpoint, Z packet),
> instead of relying on memory breakpoints.  Ah, the record target
> just ignores breakpoint insertions, and relies on forcing single-stepping
> and checking breakpoint hits itself.
> --
> Pedro Alves

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