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] |
Hi Joel, According to your mail, I make a new patch. 2008-10-08 Hui Zhu <teawater@gmail.com> Displaced stepping can be set to auto (enable in non-stop mode), on, off. * infrun.c (can_use_displaced_stepping): Change type to const char pointer. (can_use_displaced_stepping_auto): New string. (can_use_displaced_stepping_on): New string. (can_use_displaced_stepping_off): New string. (can_use_displaced_stepping_enum): New array. (use_displaced_stepping): Return non-zero if displaced stepping is auto, and can be used with GDBARCH, and in non-stop mode. Return non-zero if displaced stepping is on, and can be used with GDBARCH. (_initialize_infrun): "can-use-displaced-stepping" function change to add_setshow_enum_cmd. Thanks, Hui On Tue, Oct 7, 2008 at 20:17, Joel Brobecker <brobecker@adacore.com> wrote: >> 2008-10-07 Hui Zhu <teawater@gmail.com> >> >> * infrun.c (use_displaced_stepping): Displaced stepping just >> enable in non-stop mode. > > There is still a piece missing. Namely, allow the user to force > displaced-stepping in a mode that is not non-stop. Pedro suggested that > we either change the maint command, or add a new one. How about changing > the maint command into a mainstream command that's a tri-state: > > set use-displaced-stepping (auto|on|off) > > By default, it's "auto" which means that the debugger tries to determine > from the situation whether it's necessary or not (basically if non-stop). > But the user can then override the decision either way. > > -- > Joel >
Attachment:
displaced_step_non_step.txt
Description: Text document
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |