From: LRN <lrn1986@gmail.com>
To: gdb-patches@sourceware.org
Subject: Re: Warning when using separate debug info file
Date: Thu, 18 Apr 2019 15:53:00 -0000 [thread overview]
Message-ID: <66d48dfd-23ac-7e05-3ad8-4e65b0c1c7f9@gmail.com> (raw)
In-Reply-To: <83h8aveape.fsf@gnu.org>
[-- Attachment #1.1: Type: text/plain, Size: 929 bytes --]
On 18.04.2019 15:53, Eli Zaretskii wrote:
>> From: LRN
>> Date: Wed, 17 Apr 2019 23:06:19 +0300
>
>> I've reported it to the bugtracker, but no one seems to be interested in fixing
>> this, and i have no idea why this happens (although i do have a hypothesis).
>
> What is your hypothesis, if I may ask?
>
Found the bug report[0], by the way.
The hypothesis is...actually, no, i have no idea. I mean, it's obvious that gdb
expects to find that section in a separate debug file for some reason. Probably
because separate debug files are just PE binaries, and the code that reads them
is heavily re-used. Or maybe gdb supports recursive debuglinks?
Either way, the workaround, as you've already surmised, is to placate gdb by
adding a .gnu_debuglink section to the separate debug file. The trick is to
ensure that it passes the CRC32 check.
[0]: https://sourceware.org/bugzilla/show_bug.cgi?id=14527
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-04-18 15:53 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 [this message]
2019-04-18 18:30 ` Eli Zaretskii
2019-04-24 19:28 ` Tom Tromey
2019-04-24 19:39 ` Eli Zaretskii
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=66d48dfd-23ac-7e05-3ad8-4e65b0c1c7f9@gmail.com \
--to=lrn1986@gmail.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