This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [rfc, arm] Always use correct execution state for single-step breakpoints
- From: Tom Tromey <tromey at redhat dot com>
- To: "Ulrich Weigand" <uweigand at de dot ibm dot com>
- Cc: gdb-patches at sourceware dot org, matthew dot gretton-dann at arm dot com, patches at linaro dot org
- Date: Fri, 25 Mar 2011 09:59:10 -0600
- Subject: Re: [rfc, arm] Always use correct execution state for single-step breakpoints
- References: <201103241831.p2OIVfSm025531@d06av02.portsmouth.uk.ibm.com>
>>>>> "Ulrich" == Ulrich Weigand <uweigand@de.ibm.com> writes:
Ulrich> This is done by means of a new global "arm_override_mode" which
Ulrich> is respected in arm_pc_is_thumb unconditionally (similar to
Ulrich> arm_force_mode_string),
Ulrich> (The global is a bit ugly, but the concept still seems right to me:
Ulrich> if at some point in the future, we actually do use two different
Ulrich> gdbarch's to represent Thumb vs. ARM, the single-step routines would
Ulrich> determine the proper gdbarch to set the breakpoint in and simply
Ulrich> use insert_single_step_breakpoint with that arch.)
I wonder whether such globals should actually be per-inferior?
I really don't know whether it would be possible to get in trouble with
this.
Tom