From: Antoine Tremblay <antoine.tremblay@ericsson.com>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [PATCH v8 5/7] Support software single step on ARM in GDBServer
Date: Wed, 13 Jan 2016 19:10:00 -0000 [thread overview]
Message-ID: <5696A115.3070703@ericsson.com> (raw)
In-Reply-To: <86io2xv4oj.fsf@gmail.com>
On 01/13/2016 11:13 AM, Yao Qi wrote:
> Antoine Tremblay <antoine.tremblay@ericsson.com> writes:
>
>> +
>> +/* Get the raw next possible addresses. PC in next_pcs is the current program
>> + counter, which is assumed to be executing in ARM mode.
>> +
>> + The values returned have the execution state of the next instruction
>> + encoded in it. Use IS_THUMB_ADDR () to see whether the instruction is
>> + in Thumb-State, and gdbarch_addr_bits_remove () to get the plain memory
>> + address in GDB and arm_addr_bits_remove in GDBServer. */
>> +
>> +VEC (CORE_ADDR) *
>> +arm_get_next_pcs_raw (struct arm_get_next_pcs *self,
>> + CORE_ADDR pc)
>> +{
>> + int byte_order = self->byte_order;
>> + unsigned long pc_val;
>> + unsigned long this_instr = 0;
>> + unsigned long status;
>> + CORE_ADDR nextpc;
>> + struct regcache *regcache = self->regcache;
>> + VEC (CORE_ADDR) *next_pcs = NULL;
>> +
>> + pc_val = (unsigned long) pc;
>> + this_instr = self->ops->read_mem_uint (pc, 4, byte_order);
> ^^^^^^^^^^
>
>> -
>> -/* Get the raw next address. PC is the current program counter, in
>> - FRAME, which is assumed to be executing in ARM mode.
>> -
>> - The value returned has the execution state of the next instruction
>> - encoded in it. Use IS_THUMB_ADDR () to see whether the instruction is
>> - in Thumb-State, and gdbarch_addr_bits_remove () to get the plain memory
>> - address. */
>> -
>> -static CORE_ADDR
>> -arm_get_next_pc_raw (struct regcache *regcache, CORE_ADDR pc)
>> -{
>> - struct gdbarch *gdbarch = get_regcache_arch (regcache);
>> - enum bfd_endian byte_order = gdbarch_byte_order (gdbarch);
>> - enum bfd_endian byte_order_for_code = gdbarch_byte_order_for_code (gdbarch);
>> - unsigned long pc_val;
>> - unsigned long this_instr;
>> - unsigned long status;
>> - CORE_ADDR nextpc;
>> -
>> - pc_val = (unsigned long) pc;
>> - this_instr = read_memory_unsigned_integer (pc, 4, byte_order_for_code);
> ^^^^^^^^^^^^^^^^^^^
>
> The code change above introduces a bug as I see. The original code uses
> byte_order_for_code which is right to me, but it becomes byte_order
> after the change. Patch below fixes it.
>
Thank you!
Antoine
next prev parent reply other threads:[~2016-01-13 19:10 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-17 14:14 [PATCH v8 0/7] Support software single step and conditional breakpoints " Antoine Tremblay
2015-12-17 14:15 ` [PATCH v8 5/7] Support software single step " Antoine Tremblay
2015-12-21 13:58 ` Yao Qi
2016-01-04 12:59 ` Antoine Tremblay
2016-01-06 14:23 ` Yao Qi
2016-01-06 14:36 ` Antoine Tremblay
2016-01-06 14:56 ` Yao Qi
2016-01-06 14:58 ` Antoine Tremblay
2016-01-06 14:42 ` Yao Qi
2016-01-06 14:50 ` Antoine Tremblay
2016-01-06 15:04 ` Yao Qi
2016-01-13 16:13 ` Yao Qi
2016-01-13 19:10 ` Antoine Tremblay [this message]
2015-12-17 14:15 ` [PATCH v8 4/7] Share regcache function regcache_raw_read_unsigned Antoine Tremblay
2015-12-17 14:15 ` [PATCH v8 7/7] Enable conditional breakpoints for targets that support software single step in GDBServer Antoine Tremblay
2015-12-17 14:15 ` [PATCH v8 3/7] Refactor arm_software_single_step to use regcache Antoine Tremblay
2016-01-18 10:35 ` Yao Qi
2016-01-18 13:07 ` Yao Qi
2016-01-18 14:02 ` Antoine Tremblay
2016-01-21 7:52 ` Yao Qi
2015-12-17 14:15 ` [PATCH v8 1/7] Replace breakpoint_reinsert_addr by get_next_pcs operation in GDBServer Antoine Tremblay
2015-12-17 14:15 ` [PATCH v8 6/7] Enable software single stepping for while-stepping actions " Antoine Tremblay
2015-12-17 14:15 ` [PATCH v8 2/7] Share some ARM target dependent code from GDB with GDBServer Antoine Tremblay
2015-12-18 12:56 ` [PATCH v8 0/7] Support software single step and conditional breakpoints on ARM in GDBServer Antoine Tremblay
2015-12-18 16:45 ` Antoine Tremblay
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5696A115.3070703@ericsson.com \
--to=antoine.tremblay@ericsson.com \
--cc=gdb-patches@sourceware.org \
--cc=qiyaoltc@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox