Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Tom Tromey <tom@tromey.com>,
	 lrn1986@gmail.com,  gdb-patches@sourceware.org
Subject: Re: Warning when using separate debug info file
Date: Thu, 25 Apr 2019 15:49:00 -0000	[thread overview]
Message-ID: <87zhoeaxuu.fsf@tromey.com> (raw)
In-Reply-To: <838svyyvql.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 25 Apr	2019 18:01:38 +0300")

>>>>> "Eli" == Eli Zaretskii <eliz@gnu.org> writes:

>> I don't recall which but probably the section is either loadable or
>> allocatable in your situation.

Eli> Both, it looks:
[...]

Eli> But the question is why GDB looks for this section in the hello.debug
Eli> file, not in hello.exe.  That's what the warning emitted by GDB is
Eli> about:

When reading a separate debug file, gdb tries to ensure the section
offsets for the separate debug file are the same as the section offsets
in the main file.  To do this, it matches sections -- but only sections
that are loadable (or allocatable, like I said, I forget).

Eli> What do you get with the above objdump command on the separate debug
Eli> file?  I get an error message:

I get the same error, because my separate debug file does not include
this section.

The section isn't needed in the separate debug file -- only in the
stripped file.  What is wrong here is the section flags.

Tom


  reply	other threads:[~2019-04-25 15:49 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
2019-04-25 13:46             ` Tom Tromey
2019-04-25 15:02               ` Eli Zaretskii
2019-04-25 15:49                 ` Tom Tromey [this message]
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=87zhoeaxuu.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=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