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: [RFC] Using bt command in async mode


 > > Incidentally, the patch I've presented for bt isn't suitable for inclusion
 > > as it uses:
 > > 
 > > +
 > > +   if (restart)
 > > +     continue_command ("&", 0);
 > > 
 > > If the user interrupts with 'bt' during a step, he presumably wants the
 > > step to finish.  I'm not sure how easy it is for Gdb to jump the inferior
 > > back into it's old state of execution.
 > 
 > It's not very hard. You only need to hack continue_command not to call
 > (indirectly) the clear_proceed_status function, which currently wipes away
 > all state.

It looks a bit harder than that.  Perhaps the arguments proceed () was called
with need to be saved, as well as executing the appropriate contination
after proceed () returns.

-- 
Nick                                           http://www.inet.net.nz/~nickrob


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