From: Carlos O'Donell <carlos@baldric.uwo.ca>
To: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] [PATCH] ELF32 userspace, ELF64 kernel, and 32-bit signals on hppa. (help needed)
Date: Wed, 3 Dec 2003 15:25:46 -0500 [thread overview]
Message-ID: <20031203202546.GI11034@systemhalted> (raw)
In-Reply-To: <20031203072126.GB5828@systemhalted>
On Wed, Dec 03, 2003 at 02:21:26AM -0500, Carlos O'Donell wrote:
>
> parisc,
>
> *** Help needed, code broken ... ***
>
> There is a bug hiding in the code... I can't find it yet.
> Userspace sorta works, but sometimes processes go splat, and I think it
> has to do with the following:
>
> - In restore_context32 I have to ship the 32-bit value into a 64-bit
> registers. Should it be sign extended?
> = I think yes.
> - Is stack address 0xfffffffffaf00410 the same as 0x00000000faf00410?
> = No?
This turned out to be the issue. I just did a zero-extended load into an
unsigned variable and *everything* works now. I need to go into more
testing now.
c.
prev parent reply other threads:[~2003-12-03 20:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-03 7:21 [parisc-linux] [PATCH] ELF32 userspace, ELF64 kernel, and 32-bit signals on hppa. (help needed) Carlos O'Donell
2003-12-03 8:29 ` Joel Soete
2003-12-03 20:25 ` 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=20031203202546.GI11034@systemhalted \
--to=carlos@baldric.uwo.ca \
--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