From: Michael Snyder <msnyder@cygnus.com>
To: gdb-patches <gdb-patches@sources.redhat.com>
Cc: vinschen@redhat.com
Subject: Re: [RFA]: arm changes to run gdb.asm/asm-source.exp successfully
Date: Wed, 05 Dec 2001 13:58:00 -0000 [thread overview]
Message-ID: <3C0E97EE.4A26EA06@cygnus.com> (raw)
In-Reply-To: <20011205094959.F10634@cygbert.vinschen.de>
Corinna Vinschen wrote:
>
> On Wed, Dec 05, 2001 at 01:09:17AM +0500, Fernando Nasser wrote:
> > Corinna Vinschen wrote:
> > >
> > > Hi,
> > >
> > > the following patch allows ARM targets to run the gdb.asm test
> > > successfully. The change consists basically of a change to
> > > asm-tdep.c, function arm_skip_prologue() to scan the prologue
> > > the hard way when the source is assembler code and of adding the
> > > appropriate arm.inc file plus some additional lines in asm-source.exp
> > > and configure.in to support the new target.
> > >
> >
> > Yes, it makes sense not to use the line number information if the
> > source is assembler (until something changes in gas land, but if
> > that happens we will adapt). This part is approved, just add the word
> > "Always" to the changelog or reword it to "Do not use line number
> > information to skip the prolog if source is assembler.".
>
> Thanks, I've applied that part.
Interestingly enough, though, with the fix that I just checked in
to gas for line symbols, this GDB trick seems no longer to be necessary.
The problem was with the line symbols that GAS was emitting. There
were too many of them. Now they are perfectly OK.
next prev parent reply other threads:[~2001-12-05 21:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-04 10:34 Corinna Vinschen
2001-12-04 12:09 ` Fernando Nasser
2001-12-05 1:02 ` Corinna Vinschen
2001-12-05 13:58 ` Michael Snyder [this message]
2001-12-20 14:15 ` Corinna Vinschen
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=3C0E97EE.4A26EA06@cygnus.com \
--to=msnyder@cygnus.com \
--cc=gdb-patches@sources.redhat.com \
--cc=vinschen@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