Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Yao Qi <qiyaoltc@gmail.com>
To: Anton Kolesov <Anton.Kolesov@synopsys.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
		Francois Bedard <Francois.Bedard@synopsys.com>
Subject: Re: [PATCH 2/5] arc: Set section to ".text" when disassembling
Date: Wed, 15 Feb 2017 22:27:00 -0000	[thread overview]
Message-ID: <CAH=s-POacRUV_BBWMxt4hT0ohAO7w182tpt6AWRgaFNgU0Ru2g@mail.gmail.com> (raw)
In-Reply-To: <20170214100130.29194-2-Anton.Kolesov@synopsys.com>

On Tue, Feb 14, 2017 at 10:01 AM, Anton Kolesov
<Anton.Kolesov@synopsys.com> wrote:
> +
> +  /* ARC disassembler requires that info->section is valid - it will be used to
> +     access program headers of ELF files that is needed to distinguish between
> +     ARC EM and HS (ARC600, ARC700 and ARC v2 can be distinguished by BFD's
> +     `mach` attribute).  Without this information disassembler will default to
> +     ARC EM for ARC v2 targets, and it will not recognize instructions specific
> +     to ARC HS, for example, double-word store and load.  */
> +  if (exec_bfd != NULL)
> +    info->section = bfd_get_section_by_name (exec_bfd, ".text");

info->section should be valid, but why must it be ".text"?  Can I disassembly
instructions in .plt section?  How about using find_pc_section (addr) to get
the right section?  like mep_gdb_print_insn.

-- 
Yao (齐尧)


  reply	other threads:[~2017-02-15 22:27 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-14 10:01 [PATCH 1/5] arc: Align internal regnums with architectural regnums Anton Kolesov
2017-02-14 10:01 ` [PATCH 5/5] arc: Add prologue analysis Anton Kolesov
2017-02-14 15:51   ` Eli Zaretskii
2017-02-17 13:25   ` Pedro Alves
2017-03-15 15:18     ` [PATCH 5/5 v2] " Anton Kolesov
2017-03-15 15:59       ` Eli Zaretskii
2017-03-27 14:20       ` Anton Kolesov
2017-03-28 13:28         ` Pedro Alves
2017-02-14 10:01 ` [PATCH 4/5] arc: Add disassembler helper Anton Kolesov
2017-02-14 15:50   ` Eli Zaretskii
2017-02-17 13:00   ` Pedro Alves
2017-02-17 13:01   ` Pedro Alves
2017-02-14 10:01 ` [PATCH 2/5] arc: Set section to ".text" when disassembling Anton Kolesov
2017-02-15 22:27   ` Yao Qi [this message]
2017-02-16 16:35     ` Anton Kolesov
2017-02-17 12:31       ` Pedro Alves
2017-03-15 15:16         ` Anton Kolesov
2017-02-14 10:01 ` [PATCH 3/5] arc: Add "maintenance print arc" command prefix Anton Kolesov
2017-02-17 13:02   ` Pedro Alves
2017-02-17 13:26 ` [PATCH 1/5] arc: Align internal regnums with architectural regnums 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='CAH=s-POacRUV_BBWMxt4hT0ohAO7w182tpt6AWRgaFNgU0Ru2g@mail.gmail.com' \
    --to=qiyaoltc@gmail.com \
    --cc=Anton.Kolesov@synopsys.com \
    --cc=Francois.Bedard@synopsys.com \
    --cc=gdb-patches@sourceware.org \
    /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