Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jiong Wang <jiwang@tilera.com>
To: Pedro Alves <palves@redhat.com>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [RFC/TileGX] fix longjmp bug
Date: Fri, 01 Mar 2013 10:33:00 -0000	[thread overview]
Message-ID: <513083FD.5020205@tilera.com> (raw)
In-Reply-To: <5130836B.7090505@redhat.com>

On 03/01/2013 06:31 PM, Pedro Alves wrote:
> Thanks.
>
>> gdb/ChangeLog:
>>
>>          * tilegx-tdep.c (tilegx_get_longjmp_target): New function.
>>          (tilegx_gdbarch_init): Install it.
>>
> OK with the issues pointed out below fixed.
>
>> +/* This is the implementation of gdbarch method get_longjmp_target.  */
>> +
>> +static int
>> +tilegx_get_longjmp_target (struct frame_info *frame, CORE_ADDR *pc)
>> +{
>> +  struct gdbarch *gdbarch = get_frame_arch (frame);
>> +  enum bfd_endian byte_order = gdbarch_byte_order (gdbarch);
>> +  CORE_ADDR jb_addr;
>> +  char buf[8];
> s/char/gdb_byte/.
>
>> +
>> +  jb_addr = get_frame_register_unsigned (frame, TILEGX_R0_REGNUM);
>> +
>> +  /* TileGX jmp_buf contains 32 elements of type __uint_reg_t which
>> +     is size of 8bytes, the return address is stored in the 25th slot.  */
> Grammar:
>
>    /* TileGX's jmp_buf contains 32 elements of type __uint_reg_t which
>       has a size of 8 bytes.  The return address is stored in the 25th
>       slot.  */
>
>> +  if (target_read_memory (jb_addr +  25 * 8, buf, 8))
> should be single space ---------------^
>
> OK with these issues fixed.

   thanks for review !



-- 
Regards,
Jiong. Wang
Tilera Corporation.


  reply	other threads:[~2013-03-01 10:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-01  9:58 Jiong Wang
2013-03-01 10:31 ` Pedro Alves
2013-03-01 10:33   ` Jiong Wang [this message]
2013-03-01 13:13   ` char buf[] -> gdb_byte[] (was: Re: [RFC/TileGX] fix longjmp bug) Pedro Alves

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=513083FD.5020205@tilera.com \
    --to=jiwang@tilera.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.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