From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <glibc-bugs-return-3270-listarch-glibc-bugs=sources.redhat.com@sources.redhat.com>
Received: (qmail 28668 invoked by alias); 12 Oct 2005 05:21:04 -0000
Mailing-List: contact glibc-bugs-help@sources.redhat.com; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:glibc-bugs-subscribe@sources.redhat.com>
List-Post: <mailto:glibc-bugs@sources.redhat.com>
List-Help: <mailto:glibc-bugs-help@sources.redhat.com>, <http://sources.redhat.com/lists.html#faqs>
Sender: glibc-bugs-owner@sources.redhat.com
Received: (qmail 28655 invoked by uid 48); 12 Oct 2005 05:21:02 -0000
Date: Wed, 12 Oct 2005 05:21:00 -0000
From: "nmiell at comcast dot net" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Message-ID: <20051012052102.1468.nmiell@comcast.net>
Reply-To: sourceware-bugzilla@sourceware.org
Subject: [Bug libc/1468] New: AMD64 {get,set,swap,make}context use wrong offsets into ucontext_t
X-Bugzilla-Reason: CC
X-SW-Source: 2005-10/txt/msg00034.txt.bz2
List-Id: <glibc-bugs.sourceware.org>

The offsets into ucontext_t for fpregs, sigmask, fpregsmem, and mxcsr (as
specified in sysdeps/unix/sysv/linux/x86_64/ucontext_i.h) are wrong.

Fixing this could be a potential ABI change, although I don't see how anything
that ever used these fields could have possibly worked in the first place.

-- 
           Summary: AMD64 {get,set,swap,make}context use wrong offsets into
                    ucontext_t
           Product: glibc
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: libc
        AssignedTo: gotom at debian dot or dot jp
        ReportedBy: nmiell at comcast dot net
                CC: glibc-bugs at sources dot redhat dot com


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

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.