Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [RFC/RFA] TLS support part 2
Date: Wed, 02 Oct 2002 07:57:00 -0000	[thread overview]
Message-ID: <20021002145730.GB22578@nevyn.them.org> (raw)
In-Reply-To: <15770.63097.522572.688579@localhost.redhat.com>

On Wed, Oct 02, 2002 at 09:36:57AM -0400, Elena Zannoni wrote:
> 
> Here is the thread/target related part of the TLS support.
> 
> A new thread layer op has been added, to fetch the address of the variable.

OK, I see how it works now.  This is workable for gdbserver; I'll just
have to figure out how to ask for the link map address in some portable
way.  This will take some thinking; the best way to do it involves
noticeable protocol changes...

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2002-10-02 14:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-02  6:39 Elena Zannoni
2002-10-02  7:57 ` Daniel Jacobowitz [this message]
2002-10-02  8:29   ` Elena Zannoni
2002-10-21 12:31 ` Elena Zannoni
2002-11-07  7:01 ` Elena Zannoni
2002-11-08 12:06   ` Mark Kettenis
2002-11-08 12:20     ` Elena Zannoni
2002-11-11 18:41 ` Elena Zannoni

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=20021002145730.GB22578@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=gdb-patches@sources.redhat.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