Lines Matching refs:thumb

5 ARM thumb and gdbserver
8 When executing thumb code, the ARM cpu program counter value is
10 that the instruction being executed is a thumb instruction is
21   by gdb. As gdb is giving breakpoints without the thumb bit set,
23   the thumb bit.
25   without the thumb bit.
26   => when the guest_IP is compared with these breakpoints, the thumb bit
32   sees the correct IP. This PUT must be done with the thumb bit set,
33   as this value will be given back to gdb. gdb uses the thumb bit a.o.
36   If the thumb bit is not properly set, these commands are not working.
38   of the instruction being instrumented, the thumb bit must be accessible
41   the thumb bit).
46   At least at this moment (r2155/r11786), the extents for ARM/thumb blocks
47   contains addresses with the thumb bit set. It is not clear that this is
50   fact that the instruction is a thumb instruction.
53   to ensure it is not sensitive to the presence (or not) of the thumb
57   When the translation is requested, the thumb bit must be properly set
59   to decide to decode in ARM or in thumb mode.
60   The monitor command guesses the thumb bit based on the debug information.
62 * gdb 7.0 is buggy with thumb code
63   The logic of gdb to guess the next PC in thumb code is not working
68   - initially, IstMark contained the thumb bit in the addr.
72   - A change was done to mask the thumb bit in the IstMark
75   - So, it was needed to have the thumb bit when instrumenting an
81      * Derive the thumb bit for a SB from the extent address.
82        This was discarded as this implies that an SB cannot mix thumb
84        ARM/thumb code, which potentially decreases performance.
85        Also, it would oblige to keep the thumb bit in the extents, which
89        to obtain the guest_IP : for thumb code, this field is 1,