From: Geoff Keating <geoffk@geoffk.org>
To: ac131313@cygnus.com
Cc: gdb-patches@sources.redhat.com, binutils@sources.redhat.com
Subject: Re: properly handle extensions to DWARF 2 line number information
Date: Thu, 01 Nov 2001 12:14:00 -0000 [thread overview]
Message-ID: <200111112136.NAA29425@geoffk.org> (raw)
In-Reply-To: <3BEEA2C0.30203@cygnus.com> (message from Andrew Cagney on Sun, 11 Nov 2001 11:09:36 -0500)
> Date: Sun, 11 Nov 2001 11:09:36 -0500
> From: Andrew Cagney <ac131313@cygnus.com>
> User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:0.9.3) Gecko/20011020
> X-Accept-Language: en-us
> Cc: gdb-patches@sources.redhat.com, binutils@sources.redhat.com
>
> Er, probably not 5.1. People would probably like to see it working in
> the field first.
I see I have caught the GDB release process at a bad time. No
problem, it can wait for 5.1.1 or whatever.
Is it OK for the mainline?
The reason this came up was the following question:
> On a related matter, is there anything in an executable indicating
> which architecture an i386 binary belongs? Having a requrement that
> an (embedded) user explicitly set their architecture is pretty lame.
> The MIPS, for instance, detects and auto-selects both GDB and, if
> used, the simulator, based on information found in the executable.
The obvious way to do this is to generate and use the DWARF 3
line-number information, but while I was testing a patch to generate
it in GAS, I found that old GDB versions didn't ignore it as they
should; the effect is that a GAS that generates this produces objects
that can't usefully be debugged with a GDB without this patch.
--
- Geoffrey Keating <geoffk@geoffk.org> <geoffk@redhat.com>
next parent reply other threads:[~2001-11-11 21:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200111111226.fABCQMv05908@thief.cygnus.com>
[not found] ` <3BEEA2C0.30203@cygnus.com>
2001-11-01 12:14 ` Geoff Keating [this message]
2001-11-01 15:12 ` Elena Zannoni
2001-11-01 18:24 ` Jim Blandy
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=200111112136.NAA29425@geoffk.org \
--to=geoffk@geoffk.org \
--cc=ac131313@cygnus.com \
--cc=binutils@sources.redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=geoffk@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