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] |
2 - However I should hold this change for now because you think I should write the adjusted PC value back to the target, by adding something like "write_pc_pid (stop_pc, ecs->ptid)" I will verify the impact of such a change, and report.Good news :). Adding this does not introduce any regression, so no red dragon lurking so far...
Ya!
3 - Assuming we get all issues in this RFA resolved, then I will start looking at the addition of the software_singlestep flag.
I am starting to work on this one.
I suggest for this RFA to:
- define a new boolean software_singlestep_p
- set it at the same time we adjust the PC when detecting sw single
step.
- Change the value of not_a_sw_breakpoint in the call to
bpstat_stop_status() to prepend a "sw_single_step_p ||".
Yep,
As a next patch, we would add a new sw_single_step_p parameter to bpstat_stop_status() to pass this value separately.Somebody elses problem (hmm, perhaps we could trick DanielJ into doing it ;-)
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |