[Top] [All Lists]

Re: struct sigcontext for N32 userland

To: "Atsushi Nemoto" <>
Subject: Re: struct sigcontext for N32 userland
From: "Franck Bui-Huu" <>
Date: Tue, 13 Feb 2007 09:27:20 +0100
Domainkey-signature: a=rsa-sha1; c=nofws;; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=H2he077f/C63Emob5alCc2T3DWI4iycOEKTca4rNVrq1qi4dMFNHyGkt41B4vTw9YsoWQ/cLi9xxvVvVHSeYCExs7jX6apBMEWBqlaPrNkVenAptqWoBW9g3pfcpY7wtcZqf5F31RHDkM6s+KUGCHevNrFZRTc6dT4milY/B8Ds=
In-reply-to: <>
Original-recipient: rfc822;
References: <>
On 2/12/07, Atsushi Nemoto <> wrote:
If N32 userland refers asm-mips/sigcontext.h, struct sigcontext cause
some troubles.


struct sigcontext {
        unsigned long   sc_regs[32];

The kernel use 64-bit for sc_regs[0], and both N32/N64 userland
expects it was 64-bit.  But size of 'long' on N32 is actually 32-bit.
So this definition make some confusion.

glibc has its own sigcontext.h and it uses 'unsigned long long' for
sc_regs, so no real problem with glibc.

Just out of curiosity, for what purpose does the glibc use sigcontext ?


<Prev in Thread] Current Thread [Next in Thread>