Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Carlos O'Donell <carlos@baldric.uwo.ca>
To: Christophe Rhodes <csr21@cam.ac.uk>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] mcontext registers on parisc64
Date: Tue, 20 Aug 2002 09:22:13 -0400	[thread overview]
Message-ID: <20020820132213.GA4865@systemhalted> (raw)
In-Reply-To: <20020820114935.GA27316@cam.ac.uk>

> 
> Inspecting the sigcontext that I get on a parisc64 machine gives
> register contents looking a bit like
>     [...]
>     0xffffffff, 0xdeadbeef, 0x0, 0xf00d, 0x0, 0xfaf00380, 0x0, 0x2097a, 0x0, 
>     0xfaf001a4, 0x0, 0x2096a, 0x0, 0x1, 0x0, 0x20972, 0x0, 0x1, 0x0, 0x0, 0x0, 
>     [...]
> 
> and the alternation of data, 0/-1 is what leads me to believe that
> 64-bit quantities are being delivered; userland only seems to know about
> 32-bits, though.
> 
> Please don't hesitate to get back to me with comments and/or criticisms,
> 
> Cheers,
> Christophe

This might be a kernel bug. We should always return 32-bit quantities to 
userspace (until we get a 64-bit userspace :).

Once we straighten out the sigcontext->mcontext_t issue in glibc, we can
take a look at this. I might just patch glibc on my box tonight... and go
forward with hacking on the kernel bits.

c.

      reply	other threads:[~2002-08-20 13:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-17 22:05 [parisc-linux] subo -> overflow_trap (12) -> What to do? Carlos O'Donell
2002-08-20 11:49 ` [parisc-linux] mcontext registers on parisc64 (was Re: subo -> overflow_trap (12) -> What to do?) Christophe Rhodes
2002-08-20 13:22   ` Carlos O'Donell [this message]

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=20020820132213.GA4865@systemhalted \
    --to=carlos@baldric.uwo.ca \
    --cc=csr21@cam.ac.uk \
    --cc=parisc-linux@lists.parisc-linux.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