From: Eli Zaretskii <eliz@gnu.org>
To: LRN <lrn1986@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Warning when using separate debug info file
Date: Thu, 18 Apr 2019 12:53:00 -0000 [thread overview]
Message-ID: <83h8aveape.fsf@gnu.org> (raw)
In-Reply-To: <20439f48-c0ff-e4b2-5cfc-6bb4b594d88c@gmail.com> (message from LRN on Wed, 17 Apr 2019 23:06:19 +0300)
> From: LRN <lrn1986@gmail.com>
> Date: Wed, 17 Apr 2019 23:06:19 +0300
>
> I'm too lazy to explain this right now. Here's a Python program (attached) that
> creates separate debug info files that do not produce this warning.
So the workaround is to make the separate debug file have that
section. Not sure it's worth the hassle, since the warning is
harmless.
> 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?
Thanks.
next prev parent reply other threads:[~2019-04-18 12: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 [this message]
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
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=83h8aveape.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=lrn1986@gmail.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