This is the mail archive of the gdb-patches@sources.redhat.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]
Other format: [Raw text]

Re: STEP_SKIPS_DELAY question, sort of


Orjan Friberg wrote:

I tried implementing a fix in handle_inferior_event (the MIPS fix is in proceed). It seemed easier to step one more time when we find out that we need to, rather than to determine beforehand that we're going to have to step twice (and I couldn't determine how to pass that information).


The concept patch below illustrates what I'm trying to do; by setting another_trap in the execution control state, by the time we get to keep_going we won't insert the breakpoint and we'll instead continue single-stepping. Comments? Is this the right approach at all?

Gah. Please ignore the previous patch (and sorry); what I posted only works when doing a continue when stopped at the branch instruction. Doing a step (which leaves us in the delay slot) followed by another step (or continue for that matter) prematurely inserts the breakpoint.


--
Orjan Friberg
Axis Communications


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