From: Doug Evans <dje@google.com>
To: Tristan Gingold <gingold@adacore.com>
Cc: gdb-patches ml <gdb-patches@sourceware.org>
Subject: Re: [RFA]: no "no debugging symbols found" for separate debug
Date: Mon, 12 Oct 2009 19:12:00 -0000 [thread overview]
Message-ID: <e394668d0910121212s7da2600y116b85c89171ed79@mail.gmail.com> (raw)
In-Reply-To: <e394668d0910121204q3535fa5bs423a968391758e2f@mail.gmail.com>
On Mon, Oct 12, 2009 at 12:04 PM, Doug Evans <dje@google.com> wrote:
>
> On Mon, Oct 12, 2009 at 6:57 AM, Tristan Gingold <gingold@adacore.com> wrote:
>>
>> Hi,
>>
>> when a stripped executable with a separate debug file is loaded, gdb prints "no debugging symbols found".
>> I think this is confusing and this was not printed in gdb 6.8
>>
>> The reason is that only the objfile is checked, not the separate debug file.
>>
>> This patch fixes that and add a test in the sepdebug.exp file.
>>
>> Tristan.
>>
>> 2009-10-12 Tristan Gingold <gingold@adacore.com>
>>
>> * objfiles.c (objfile_has_symbols): New function.
>> * objfiles.h (objfile_has_symbols): Add prototype.
>> * symfile.c (symbol_file_add_with_addrs_or_offsets): Call
>> objfile_has_symbols.
>> (reread_symbols): Ditto.
>>
>> testsuite/
>> 2009-10-12 Tristan Gingold <gingold@adacore.com>
>>
>> * gdb.base/sepdebug.exp: Check debug info are found.
>>
>
> Thanks. Tom pointed this out and it's on my todo list. Or was.
>
> This is ok with me.
> Thanks again.
>
Apologies for the resend. Gmail sent the reply as text/html. Sigh.
One nit:
+ or throught its the separate debug file. */
s/throught its the/through its/
next prev parent reply other threads:[~2009-10-12 19:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-12 13:57 Tristan Gingold
[not found] ` <e394668d0910121204q3535fa5bs423a968391758e2f@mail.gmail.com>
2009-10-12 19:12 ` Doug Evans [this message]
2009-10-13 7:58 ` Tristan Gingold
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=e394668d0910121212s7da2600y116b85c89171ed79@mail.gmail.com \
--to=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=gingold@adacore.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