Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Gary Funck <gary@intrepid.com>
To: Vinay Sridhar <vinay@linux.vnet.ibm.com>
Cc: Jan Kratochvil <jan.kratochvil@redhat.com>,
	gdb-patches@sources.redhat.com,
	        Daniel Jacobowitz <drow@false.org>,
	luisgpm@linux.vnet.ibm.com,         uweigand@de.ibm.com
Subject: Re: [patch] Accessing tls variables across files causes a bug
Date: Thu, 27 Nov 2008 15:01:00 -0000	[thread overview]
Message-ID: <20081126172332.GE19317@intrepid.com> (raw)
In-Reply-To: <1221019993.4923.3.camel@localhost.localdomain>

On 09/10/08 09:43:13, Vinay Sridhar wrote:
> Any idea when the below changes are likely to go in?

Recently, we've run into a situation where we need this bug fix.
I've corresponded with Jan on this, and he mentioned
that the fix may have some unknown impact or regressions on
the main line (though none that he knows of), and that
this patch is pending review, before it can be committed.

Have the GDB maintainers had a chance to review this patch?
Is there anything that I can do to help move it along?

thanks,

- Gary


  reply	other threads:[~2008-11-26 17:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-10  4:24 [Fwd: Re: [patch] Re: Accessing tls variables across files causes a bug] Vinay Sridhar
2008-11-27 15:01 ` Gary Funck [this message]
2008-11-27 17:07   ` [patch] Accessing tls variables across files causes a bug Jan Kratochvil
2008-12-01 14:15     ` Jan Kratochvil
2008-12-01 18:30       ` Ulrich Weigand
     [not found]     ` <20081201182931.GA18248@intrepid.com>
2008-12-01 21:54       ` Jan Kratochvil
2008-12-02 13:54         ` Ulrich Weigand
2008-12-02 14:53           ` Gary Funck
2008-12-02 15:13             ` Jan Kratochvil
2008-12-02 15:40               ` Gary Funck

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=20081126172332.GE19317@intrepid.com \
    --to=gary@intrepid.com \
    --cc=drow@false.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jan.kratochvil@redhat.com \
    --cc=luisgpm@linux.vnet.ibm.com \
    --cc=uweigand@de.ibm.com \
    --cc=vinay@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