Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Wei-cheng Wang <cole945@gmail.com>
To: Yao Qi <yao@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 1/5] Code for nds32 target
Date: Thu, 11 Jul 2013 14:26:00 -0000	[thread overview]
Message-ID: <CAPmZyH63Dzmv_zkgrXxTFwHCBBByBGqk75_FtT1nCJ_yPHBd1Q@mail.gmail.com> (raw)
In-Reply-To: <51DCF32E.9020303@codesourcery.com>

On Wed, Jul 10, 2013 at 1:37 PM, Yao Qi <yao@codesourcery.com> wrote:
> On 07/08/2013 05:27 PM, Wei-cheng Wang wrote:
> Here is the 2nd half.
>> +  struct cleanup *back_to;
>> +
>> +  /* Reload symtab if abfd changed.
> I am sorry that I can't get the points of doing this.  Can you elaborate
> please?

  I've revised the comment as such.

  /* When disassembling ex9 instructions, they are annotated with
     the original instructions at the end of line.  For example,

        0x00500122 <+82>:    ex9.it #4          ! movi $r13, 10

     Dissembler needs the symbol table to extract the original instruction
     in _ITB_BASE_ table.  If the object file is changed, reload symbol
     table.  */

>> +
>> +/* Callback for "nds32 dump" command.
>> +
>> +   Dump current register and stack for debug gdb.  */
>> +
> Do we really need this command?  You can examine registers via command 'info
> registers', and examine stack as a piece of memory via command 'x'.

  This was used to dump registers and stack and create a gdbinit script,
  so I can use the script to debug backtrace porting issues.
  Anyway, I've removed this command in revised patch.  I think I don't need
  it anymore.

> The last but not least, the binutils patch hasn't go in yet, so it is pity
> that I can't build GDB with you patches for nds32 target.
  It still needs more work :p
> You also need a news entry in gdb/NEWS about this new port.  Open gdb/NEWS,
> and then you will know how to add one entry for nds32 port :)
  Just add our target and send a separate patch for it?

Wei-cheng


      parent reply	other threads:[~2013-07-11 14:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-08  9:28 Wei-cheng Wang
2013-07-08 23:58 ` Joseph S. Myers
2013-07-09 16:18   ` Wei-cheng Wang
2013-07-09  4:10 ` Yao Qi
2013-07-09 18:23   ` Wei-cheng Wang
2013-07-25  2:35     ` Yao Qi
2013-07-10  5:38 ` Yao Qi
2013-07-11 14:06   ` Wei-cheng Wang
2013-07-11 14:26   ` Wei-cheng Wang [this message]

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=CAPmZyH63Dzmv_zkgrXxTFwHCBBByBGqk75_FtT1nCJ_yPHBd1Q@mail.gmail.com \
    --to=cole945@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=yao@codesourcery.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