From: Dan Malek <dan@mvista.com>
To: jekacur@ca.ibm.com
Cc: linux-kernel@vger.kernel.org, linuxppc-dev@lists.linuxppc.org
Subject: Re: [Fwd: sigcontext on Linux-ppc in user space]
Date: Thu, 25 Jan 2001 13:11:59 -0500 [thread overview]
Message-ID: <3A706C6F.4357762E@mvista.com> (raw)
In-Reply-To: <OF38EA3C4D.2A886AF4-ON852569DF.00530F62@LocalDomain>
jekacur@ca.ibm.com wrote:
> ...... But I
> still can't get at the sigcontext.c on Linux Powerpc. For example, this
> simple program gives me a segmentation fault. (Linux ppc, suse 6.4, kernel
> 2.2.14
You are not the only one. I recently discovered some inconsistent
data structures and function calls (sigaction, old_sigaction, different
context structures, etc.). I spent some time trying to sort it out
but didn't have enough time. I was fortunate and just bailed out using
old signal handler semantics. I was using what I believed were the
latest glibc2.1, and also the latest 2.4 kernels (which is what I
was really developing and testing). I mentioned this to some folks
closer to the glibc action, but haven't followed up. Something is
amiss here with PowerPC.
Sorry I can't provide a solution.
-- Dan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-25 18:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-25 15:09 [Fwd: sigcontext on Linux-ppc in user space] jekacur
2001-01-25 18:11 ` Dan Malek [this message]
2001-01-25 19:03 ` Roman Zippel
-- strict thread matches above, loose matches on Subject: below --
2001-01-25 18:10 Kevin B. Hendricks
2001-01-25 20:24 ` iweiny
2001-01-25 18:44 Kevin B. Hendricks
2001-01-25 18:50 jekacur
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=3A706C6F.4357762E@mvista.com \
--to=dan@mvista.com \
--cc=jekacur@ca.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--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 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.