This is the mail archive of the gdb-patches@sourceware.cygnus.com 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]

Re: RFA: revised implementation of permanent breakpoints


Jim Blandy wrote:

> + @item SKIP_PERMANENT_BREAKPOINT
> + Step the inferior past a permanent breakpoint.  GDB normally steps over
> + a breakpoint by removing it, stepping one instruction, and re-inserting
> + the breakpoint.  However, permanent breakpoints are hardwired into the
> + inferior, and can't be removed, so this strategy doesn't work.  Calling
> + SKIP_PERMANENT_BREAKPOINT adjusts the processor's state so that
> + execution will resume just after the breakpoint.  This macro does the
> + right thing even when the breakpoint is in the delay slot of a branch or
> + jump.
> +

Could I suggest adjusting the opening line so that it doesn't mention
the word ``step''?  Perhaps something like ``Adjust the target state so
that execution is resumed just after the permanent breakpoint
instruction''.  As you go on to explain, ``step'' in the traditional GDB
speak has many other connotations.

enjoy,
	Andrew

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