Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Kevin Buettner <kevinb@redhat.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] gdbserver: Add support for qGetTLSAddr packet
Date: Fri, 25 Feb 2005 21:19:00 -0000	[thread overview]
Message-ID: <20050225093429.1ea6e639@ironwood.lan> (raw)
In-Reply-To: <20050224205324.GD11751@nevyn.them.org>

On Thu, 24 Feb 2005 15:53:24 -0500
Daniel Jacobowitz <drow@false.org> wrote:

> On Mon, Dec 06, 2004 at 03:20:02PM -0700, Kevin Buettner wrote:
> > The patch below adds qGetTLSAddr packet support to gdbserver.
> > 
> > I wrote this to demonstrate / test the support that I've added on the
> > GDB side.  I suspect some configury tweaking may be needed to test for
> > the existence of td_thr_tls_get_addr() in libthread_db.c.  (If it
> > doesn't exist, then get_thread_local_addr() should be ifdef'd to return
> > a 0 status.)
> > 
> > If it's otherwise okay, I'm willing to make the necessary configury
> > changes.  If it's not okay for some other reason, I'd like to address
> > that first...
> 
> This should go through the target vector, instead of adding #ifdefs.
> Then linux-low.c can handle whether thread-db is present or not.
> 
> Is this patch still current, or did the protocol evolve since the last
> posting?

The protocol did change, but the patch is still current.  (The protocol
change simply removed the extra load module related parameters that Linux
didn't use anyway.)

Kevin


  reply	other threads:[~2005-02-25 16:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-06 22:37 Kevin Buettner
2004-12-06 23:48 ` Andreas Schwab
2005-02-25 15:52 ` Daniel Jacobowitz
2005-02-25 21:19   ` Kevin Buettner [this message]
2005-05-01 23:25     ` Daniel Jacobowitz
2005-05-05 20:05       ` Kevin Buettner

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=20050225093429.1ea6e639@ironwood.lan \
    --to=kevinb@redhat.com \
    --cc=drow@false.org \
    --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