From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Andreas Arnez <arnez@linux.vnet.ibm.com>
Cc: gdb-patches@sourceware.org, Andreas Krebbel <krebbel@linux.vnet.ibm.com>
Subject: Re: [PATCH] Skip VDSO when reading SO list
Date: Fri, 20 Sep 2013 18:14:00 -0000 [thread overview]
Message-ID: <20130920181359.GA29967@host2.jankratochvil.net> (raw)
In-Reply-To: <87siwzpgx4.fsf@br87z6lw.de.ibm.com>
On Fri, 20 Sep 2013 19:00:07 +0200, Andreas Arnez wrote:
> Jan Kratochvil <jan.kratochvil@redhat.com> writes:
> > Here should be also '&& ignore_first'.
>
> Hm, this shouldn't be necessary, because 'first' is only set when
> 'ignore_first' is set. Or did I miss something?
I agree now, replied in another mail.
> >> + {
> >> + do_cleanups (old_chain);
> >> + continue;
> >> + }
> >
> > And move this block below so that the condition is evaluated only if
> > target_read_string has really failed.
> >
> > The purpose is that no workarounds should complicate the code in the case the
> > system components are already bug-free (after glibc gets fixed).
>
> That's a good point. Still, after thinking about this some more, I
> prefer the order in the original patch, because it prevents a bogus
> l_name from being detected in a second scan when the core dump is
> debugged on a system with a different glibc version. Users may also
> experience this after a glibc update. Thoughts?
If you use non-matching glibc then it should complain. In such case there is
a pointer to some real string so it is correct GDB tries to read it as
a library. While the library load will fail it does not block trying to debug
such a core file.
A bit off-topic but for the non-matching libraries I should upstream the patch
(plus some related patches therein)
http://pkgs.fedoraproject.org/cgit/gdb.git/tree/gdb-6.6-buildid-locate.patch
as then it does not try to load non-matching executable/libraries at all.
Thanks,
Jan
prev parent reply other threads:[~2013-09-20 18:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-19 14:44 Andreas Arnez
2013-08-19 18:30 ` Jan Kratochvil
2013-08-19 20:42 ` Joel Brobecker
2013-08-19 20:47 ` Jan Kratochvil
2013-08-19 21:13 ` Joel Brobecker
2013-08-20 11:44 ` Andreas Arnez
2013-08-20 13:47 ` Jan Kratochvil
2013-09-20 13:15 ` Jan Kratochvil
2013-09-20 15:27 ` Jan Kratochvil
2013-09-20 17:00 ` Andreas Arnez
2013-09-20 18:14 ` Jan Kratochvil [this message]
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=20130920181359.GA29967@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=arnez@linux.vnet.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=krebbel@linux.vnet.ibm.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