From: iweiny@pacbell.net
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: [Fwd: sigcontext on Linux-ppc in user space]
Date: Thu, 25 Jan 2001 12:24:52 -0800 (PST) [thread overview]
Message-ID: <200101252024.MAA01557@batcave2.batcave> (raw)
In-Reply-To: <200101251810.f0PIAeH04079@ashley.ivey.uwo.ca>
I don't know if this helps or not but,
I get similar results from my 2 machines.
Machine 1 (2.2.18 glibc 2.1.3-4e)
12:17pm >./a.out
SIGUSR1 = 10
scp = 7ffff694
scp->signal = 0
Machine 2 (2.4.1 glibc 2.1.3-4e) <= very recent BK kernel
11:21am >./a.out
SIGUSR1 = 10
scp = 7ffff634
scp->signal = 0
Ira
--- To quote Kevin B. Hendricks: ---
>
>
> Hi,
>
> Here is what I get from running it on my system (ppc linux with 2.2.15 kernel with some mods and glibc-2.1.3).
>
> But no segfault.
>
> Kevin
>
>
> [kbhend@localhost ~]$ gcc -O2 -ojunk junk.c
> [kbhend@localhost ~]$ ./junk
> SIGUSR1 = 10
> scp = 7fffe9a4
> scp->signal = 0
> [kbhend@localhost ~]$
>
>
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next parent reply other threads:[~2001-01-25 20:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200101251810.f0PIAeH04079@ashley.ivey.uwo.ca>
2001-01-25 20:24 ` iweiny [this message]
[not found] <OF38EA3C4D.2A886AF4-ON852569DF.00530F62@LocalDomain>
2001-01-25 19:03 ` [Fwd: sigcontext on Linux-ppc in user space] Roman Zippel
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=200101252024.MAA01557@batcave2.batcave \
--to=iweiny@pacbell.net \
--cc=linuxppc-dev@lists.linuxppc.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