From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tom@tromey.com>
Cc: lrn1986@gmail.com, gdb-patches@sourceware.org
Subject: Re: Warning when using separate debug info file
Date: Wed, 24 Apr 2019 19:39:00 -0000 [thread overview]
Message-ID: <83mukf19dl.fsf@gnu.org> (raw)
In-Reply-To: <87k1fjfbio.fsf@tromey.com> (message from Tom Tromey on Wed, 24 Apr 2019 13:28:47 -0600)
> From: Tom Tromey <tom@tromey.com>
> Cc: LRN <lrn1986@gmail.com>, gdb-patches@sourceware.org
> Date: Wed, 24 Apr 2019 13:28:47 -0600
>
> Eli> But then why doesn't this happen on GNU/Linux?
>
> Those platforms moved away from the .gnu_debuglink approach to use
> build-id instead. See (info "(gdb) Separate Debug Files")
So you are saying that if you create a separate debug info file with
.gnu_debuglink on GNU/Linux, then GDB will display the same warning
when debugging the stripped binary? I think someone said this didn't
happen on GNU/Linux.
> So I suppose this is just a bug but the cause remains unknown.
The place where this happens, addr_info_make_relative, maps addresses
to BFD addresses, and I wonder why .gnu_debuglink appears in the array
of sections the GDB looks up in the separate debug file. Any ideas
why this happens?
next prev parent reply other threads:[~2019-04-24 19:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <83y348edoi.fsf@gnu.org>
2019-04-17 20:06 ` LRN
2019-04-18 12:53 ` Eli Zaretskii
2019-04-18 15:53 ` LRN
2019-04-18 18:30 ` Eli Zaretskii
2019-04-24 19:28 ` Tom Tromey
2019-04-24 19:39 ` Eli Zaretskii [this message]
2019-04-25 13:46 ` Tom Tromey
2019-04-25 15:02 ` Eli Zaretskii
2019-04-25 15:49 ` Tom Tromey
2019-04-25 16:19 ` Eli Zaretskii
2019-04-25 17:31 ` Tom Tromey
2019-04-27 15:19 ` Eli Zaretskii
2019-04-27 15:37 ` Eli Zaretskii
2019-05-02 15:50 ` Eli Zaretskii
2019-05-02 18:20 ` Tom Tromey
2019-05-03 7:05 ` Eli Zaretskii
2019-04-24 19:49 ` André Pönitz
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=83mukf19dl.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=lrn1986@gmail.com \
--cc=tom@tromey.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