From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: gdb-patches@sourceware.org
Subject: Re: [patch] Fix false separate debuginfo warning for no .debug suffix [Re: Recent separate debug file warning caused Debian regressions]
Date: Wed, 04 Nov 2009 23:26:00 -0000 [thread overview]
Message-ID: <20091104232643.GA15891@host0.dyn.jankratochvil.net> (raw)
In-Reply-To: <20091103170004.GA915@caradoc.them.org>
On Tue, 03 Nov 2009 18:00:04 +0100, Daniel Jacobowitz wrote:
> On Tue, Nov 03, 2009 at 11:44:19AM +0100, Jan Kratochvil wrote:
> > gdb/
> > 2009-11-03 Jan Kratochvil <jan.kratochvil@redhat.com>
> >
> > * symfile.c (separate_debug_file_exists): Change parameter parent_name
> > to parent_objfile. New variables parent_stat and abfd_stat. Call
> > strcmp and then bfd_stat functions to verify if NAME matches.
> > (find_separate_debug_file): Update the passed parameter at caller.
>
> Thanks! This is OK.
FYI now waiting on getting resolved:
[patch, configures] Unify AC_SYS_LARGEFILE exception across dirs
http://gcc.gnu.org/ml/gcc-patches/2009-11/msg00230.html
for a proper form of check-in for:
[patch] AC_SYS_LARGEFILE
http://sourceware.org/ml/gdb-patches/2009-11/msg00047.html
which is a prerequisite of this patch. I hope the regression is not so urgent
to require a temporary workaround instead.
Sorry,
Jan
next prev parent reply other threads:[~2009-11-04 23:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-02 21:53 Recent separate debug file warning caused Debian regressions Daniel Jacobowitz
2009-11-03 10:44 ` [patch] Fix false separate debuginfo warning for no .debug suffix [Re: Recent separate debug file warning caused Debian regressions] Jan Kratochvil
2009-11-03 17:00 ` Daniel Jacobowitz
2009-11-04 23:26 ` Jan Kratochvil [this message]
2009-11-05 20:04 ` Daniel Jacobowitz
2009-11-11 5:05 ` Jan Kratochvil
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=20091104232643.GA15891@host0.dyn.jankratochvil.net \
--to=jan.kratochvil@redhat.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