Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <kettenis@wins.uva.nl>
To: drepper@cygnus.com
Cc: libc-alpha@sources.redhat.com, gdb@sources.redhat.com
Subject: Re: Debugging multi-threaded SSE using programs
Date: Sun, 02 Sep 2001 05:26:00 -0000	[thread overview]
Message-ID: <200109021226.f82CQKh18978@delius.kettenis.local> (raw)
In-Reply-To: <m3d75amw7c.fsf@otr.mynet>

   From: Ulrich Drepper <drepper@redhat.com>
   Date: 01 Sep 2001 14:34:47 -0700

   Mark Kettenis <kettenis@wins.uva.nl> writes:

   > Would it be OK to provide an implementation of these calls for Linux
   > x86 that manages the SSE registers?

   Yes.  But please try to make it a bit generic so that it can be used
   with the different registers extensions already out there and also has
   room if there are yet more extensions to come.

I did some reverse-engineering on sparc-sun-solaris2.6, and it seems
that we can punt any interpretation of these extra registers to the
debugger.  In libthread_db we should simply call ps_lgetxregsize,
ps_lgetxregs or ps_lsetxregs with the appropriate arguments, or return
an appropraite error code.  This means that we cannot zero out the
register set when a thread already terminated as we do for
td_thr_getfpregs.  So be it.  Any debugger will need to deal with it.

Since the current libthread_db doesn't require ps_lgetxregsize,
ps_lgetxregs and ps_lsetxregs, I probably should use weak references
for these functions, shouldn't I?

Mark


  reply	other threads:[~2001-09-02  5:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-01 14:29 Mark Kettenis
2001-09-01 14:42 ` Ulrich Drepper
2001-09-02  5:26   ` Mark Kettenis [this message]
2001-09-02 10:47     ` Ulrich Drepper

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=200109021226.f82CQKh18978@delius.kettenis.local \
    --to=kettenis@wins.uva.nl \
    --cc=drepper@cygnus.com \
    --cc=gdb@sources.redhat.com \
    --cc=libc-alpha@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