public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tdep/15420] Thread support broken on 64-bit Solaris/x86
Date: Fri, 10 May 2013 12:10:00 -0000	[thread overview]
Message-ID: <bug-15420-4717-WLp8sQIGop@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-15420-4717@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=15420

--- Comment #5 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> 2013-05-10 12:10:22 UTC ---
CVSROOT:    /cvs/src
Module name:    src
Changes by:    brobecke@sourceware.org    2013-05-10 12:10:20

Modified files:
    gdb            : ChangeLog configure configure.ac sol-thread.c 
Removed files:
    gdb            : sparc-sol-thread.c 

Log message:
    move sparc-sol-thread.c back into sol-thread.c.

    The routines in sparc-sol-thread used to be SPARC-specific (and
    documented as such in the ptrace man page), and therefore hosting them
    in a sparc-specific file made sense.  However, newer versions of
    Solaris now use those callbacks (Solaris 10 Update 10, apparently),
    and thus the note about these callbacks being specific to SPARC
    was removed.

    So this patch deletes sparc-sol-thread.c and moves the code back
    inside sol-thread.c.

    gdb/ChangeLog:

    PR tdep/15420:
    * sol-thread.c (ps_lgetxregsize, ps_lgetxregs, ps_lsetxregs):
    New functions, directly copied from sparc-sol-thread.c.
    * sparc-sol-thread.c: Delete.
    * configure.ac: Remove code handling sparc-solaris-thread.c.
    * configure: Regenerate.

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/src/gdb/ChangeLog.diff?cvsroot=src&r1=1.15540&r2=1.15541
http://sourceware.org/cgi-bin/cvsweb.cgi/src/gdb/configure.diff?cvsroot=src&r1=1.389&r2=1.390
http://sourceware.org/cgi-bin/cvsweb.cgi/src/gdb/configure.ac.diff?cvsroot=src&r1=1.201&r2=1.202
http://sourceware.org/cgi-bin/cvsweb.cgi/src/gdb/sol-thread.c.diff?cvsroot=src&r1=1.100&r2=1.101
http://sourceware.org/cgi-bin/cvsweb.cgi/src/gdb/sparc-sol-thread.c.diff?cvsroot=src&r1=1.2&r2=NONE

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


  parent reply	other threads:[~2013-05-10 12:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-30 14:56 [Bug tdep/15420] New: " ro at TechFak dot Uni-Bielefeld.DE
2013-05-01  6:43 ` [Bug tdep/15420] " brobecker at gnat dot com
2013-05-06 11:35 ` brobecker at gnat dot com
2013-05-06 11:48 ` ro at CeBiTec dot Uni-Bielefeld.DE
2013-05-06 12:12 ` brobecker at gnat dot com
2013-05-10 12:10 ` cvs-commit at gcc dot gnu.org [this message]
2013-05-10 12:30 ` cvs-commit at gcc dot gnu.org
2013-05-10 12:37 ` brobecker at gnat dot com
2021-09-10 19:35 ` mehmetgelisin at aol dot com
2021-09-22 16:58 ` mervegunesli at aol dot com
2021-09-22 17:00 ` mark at klomp dot org

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=bug-15420-4717-WLp8sQIGop@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).