From: Grant Grundler <grundler@parisc-linux.org>
To: Carlos O'Donell <carlos@baldric.uwo.ca>
Cc: "Boehm, Hans" <hans_boehm@hp.com>,
"'parisc-linux@lists.parisc-linux.org'"
<parisc-linux@lists.parisc-linux.org>
Subject: Re: [parisc-linux] Program counter from sigcontext, constructurs and -fPIC
Date: Tue, 29 Apr 2003 16:13:57 -0600 [thread overview]
Message-ID: <20030429221357.GD17313@dsl2.external.hp.com> (raw)
In-Reply-To: <20030429213027.GB12492@systemhalted>
On Tue, Apr 29, 2003 at 05:30:28PM -0400, Carlos O'Donell wrote:
> > 3) Adding 24 bytes to the struct sigcontext pointer (?) passed as a third argument to the signal handler. (!)
>
> Are you still using a 64-bit kernel?
no - he's using:
grundler@debian:~$ uname -a
Linux debian 2.4.20-pa28 #39 Wed Mar 12 19:24:25 PST 2003 parisc unknown
unknown GNU/Linux
It's possible the kernel-headers he's using aren't clean.
Just in case, can you tell me which ones he should be using?
> What glibc version is installed? I made recent changes to mache the
> userspace and kernel versions of sigcontext (now a machine context).
grundler@debian:~$ dpkg -l libc6\*
Desired=Unknown/Install/Remove/Purge/Hold
|
Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err:
uppercase=bad)
||/ Name Version Description
+++-==============-==============-============================================
ii libc6 2.3.1-16 GNU C Library: Shared libraries and Timezone
un libc6-bin <none> (no description available)
pn libc6-dbg <none> (no description available)
ii libc6-dev 2.3.1-16 GNU C Library: Development Libraries and Hea
...
grundler@debian:~$ ls -l /var/opt/LinuxCOE/Debian/pool/main/g/glibc/libc6-dev_2.3.1-*_hppa.deb
-rw-rw-r-- 1 root 1176 2958496 Mar 22 12:02 /var/opt/LinuxCOE/Debian/pool/main/g/glibc/libc6-dev_2.3.1-16_hppa.deb
-rw-rw-r-- 1 root 1176 2959794 Apr 21 06:47 /var/opt/LinuxCOE/Debian/pool/main/g/glibc/libc6-dev_2.3.1-17_hppa.deb
I'm ok with updating to -17 if you promise it won't do evil things
to my box. ;^)
thanks,
grant
next prev parent reply other threads:[~2003-04-29 22:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-29 21:17 [parisc-linux] Program counter from sigcontext, constructurs and -fPIC Boehm, Hans
2003-04-29 21:30 ` Carlos O'Donell
2003-04-29 22:13 ` Grant Grundler [this message]
2003-04-30 0:31 ` Carlos O'Donell
2003-04-30 5:18 ` Grant Grundler
2003-04-30 7:15 ` Joel Soete
2003-04-30 18:12 ` Carlos O'Donell
2003-05-03 20:48 ` Joel Soete
2003-05-05 6:08 ` Joel Soete
2003-05-01 4:09 ` Grant Grundler
-- strict thread matches above, loose matches on Subject: below --
2003-04-30 0:52 Boehm, Hans
2003-04-25 19:40 Boehm, Hans
2003-04-25 20:52 ` Carlos O'Donell
2003-04-25 17:46 Boehm, Hans
2003-04-25 18:54 ` Carlos O'Donell
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=20030429221357.GD17313@dsl2.external.hp.com \
--to=grundler@parisc-linux.org \
--cc=carlos@baldric.uwo.ca \
--cc=hans_boehm@hp.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.