Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Andreas Arnez <arnez@linux.vnet.ibm.com>,
	gdb-patches@sourceware.org,
	Andreas Krebbel <krebbel@linux.vnet.ibm.com>
Subject: Re: [PATCH] Skip VDSO when reading SO list
Date: Mon, 19 Aug 2013 21:13:00 -0000	[thread overview]
Message-ID: <20130819211354.GE4346@adacore.com> (raw)
In-Reply-To: <20130819204625.GA8918@host2.jankratochvil.net>

> With the GDB workaround in place it may be difficult to justify the
> glibc fix.  When glibc behaves correctly in the future then I think we
> can start talking about GDB workarounds for older glibcs.

I can understand your rationale. I've had situations like that,
at work. Unfortunately for me, I was always on the other side
of the fence, getting hurt so that the pressure could remain
on those whom we expected the fix from. It's a bit unfortunate,
but if you believe it is necessary, then so be it.

> Another thing would be if you do not agree with the glibc patch; but
> that is not the case here I think.

Not at all. The rationale is as you said: Although the fix will
hopefully eventually find itself in glibc, some users will still
be using older systems where the fix is missing. If we can help
those people (again, without hurting other users - or your chances
to get the glibc patch in), then let's do it.

-- 
Joel


  reply	other threads:[~2013-08-19 21:13 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 [this message]
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

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=20130819211354.GE4346@adacore.com \
    --to=brobecker@adacore.com \
    --cc=arnez@linux.vnet.ibm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    --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