All of lore.kernel.org
 help / color / mirror / Atom feed
From: jekacur@ca.ibm.com
To: khendricks@ivey.uwo.ca
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:50:48 -0500	[thread overview]
Message-ID: <OF391E2A9A.4D8058CB-ON852569DF.00675165@LocalDomain> (raw)


Ok, actually the segfault was for a more complicated function, but the
simplified example still gives the wrong answer. i.e scp should point to a
struct sigcontext and scp->signal should be 10 in the sample program.

John Kacur/Toronto/IBM@IBMCA
jekacur@ca.ibm.com
(416) 448-2584 (phone)
778-2584 (tie line)


"Kevin B. Hendricks" <khendricks@ivey.uwo.ca> on 01/25/2001 01:10:40 PM

Please respond to khendricks@ivey.uwo.ca

To:   John Kacur/Toronto/IBM@IBMCA
cc:   linux-kernel@vger.kernel.org, linuxppc-dev@lists.linuxppc.org
Subject:  Re: [Fwd: sigcontext on Linux-ppc in user space]


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 ~]$




On Thursday, January 25, 2001, at 10:09 AM, jekacur@ca.ibm.com wrote:

> #include <stdio.h>
> #include <signal.h>
>
> /* Function Prototypes */
> void install_sigusr1_handler(void);
> void sigusr_handler(int , siginfo_t *, struct sigcontext * scp);
>
> int main(void)
> {
>         install_sigusr1_handler();
>         printf("SIGUSR1 = %d\n", SIGUSR1);
>         raise(SIGUSR1);
>         exit(0);
> }
>
> void install_sigusr1_handler(void)
> {
>         struct sigaction newAct;
>
>         if (sigemptyset(&newAct.sa_mask) != 0) {
>                 fprintf(stderr, "Warning, sigemptyset failed.\n");
>         }
>
>         newAct.sa_flags = 0;
>         newAct.sa_flags |= SA_SIGINFO | SA_RESTART;
>
>         newAct.sa_sigaction = (void
> (*)(int,siginfo_t*,void*))sigusr_handler;
>
>         if (sigaction(SIGUSR1, &newAct, NULL) != 0) {
>                 fprintf(stderr, "Couldn't install SIGUSR1 handler.\n");
>                 fprintf(stderr, "Exiting.\n");
>                 exit(1);
>         }
> }
>
> void sigusr_handler(int signo, siginfo_t *siginfp, struct sigcontext *
scp)
> {
>         printf("scp = %08x\n", scp);
>         printf("scp->signal = %d\n", scp->signal);
> }
>
>




-
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/

             reply	other threads:[~2001-01-25 18:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-25 18:50 jekacur [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-01-25 18:44 [Fwd: sigcontext on Linux-ppc in user space] Kevin B. Hendricks
2001-01-25 18:10 Kevin B. Hendricks
2001-01-25 20:24 ` iweiny
2001-01-25 15:09 jekacur
2001-01-25 18:11 ` Dan Malek
2001-01-25 19:03 ` 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=OF391E2A9A.4D8058CB-ON852569DF.00675165@LocalDomain \
    --to=jekacur@ca.ibm.com \
    --cc=khendricks@ivey.uwo.ca \
    --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.