This is the mail archive of the gdb@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] |
On Tue, Feb 18, 2003 at 09:29:58AM -0700, Kevin Buettner wrote:On Feb 17, 9:04pm, Andrew Cagney wrote:> If GDB implements software single step, then the `s' packet is never > used. Consequently, requiring the unconditional implementation of "s" > makes little sense.
Kevin wrote:
It should but the interaction is weird. remote.c doesn't see the "" reply until target_wait() is called. This means that the target_wait() method would need to be modified to handle this. I guess it could record this and then return immedatly with a TARGET_WAITKIND_SPURIOUS. Kind of vaguely like how some of the other packets are handled.What about the situation where GDB implements software single step AND the stub implements the 's' packet? Shouldn't GDB at least attempt to see if the stub supports the 's' packet before deciding to never send it?
No. The relevant comments read:In my humble opinion, SOFTWARE_SINGLE_STEP should affect native code and not remote;
[For remote MIPS/Linux targets, I've found some cases where GDB's implementation of software singlestep causes some undesirable behavior when doing the 'stepi' operation through some code that's hit by a number of threads. Yet, when software single step is implemented in the debug agent (and disabled in GDB), the debugging behavior is much more useful (and sensible).]Is it just slow, or do different things actually happen?
It is just very slow. Andrew
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |