public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Camm Maguire <camm@enhanced.com>
To: linux-kernel@vger.kernel.org
Subject: 2.2.x kernels not filling in siginfo_t.si_addr on SEGV?
Date: Thu, 08 Mar 2001 17:27:50 -0500	[thread overview]
Message-ID: <E14b8sw-0007A2-00@intech19.enhanced.com> (raw)

Greetings!  Shouldn't a SIGSEGV fill in th si_addr member of the
siginfo_t structure passed to a signal handler?  Here is what I see
(on several archs):
=============================================================================
q.c
=============================================================================
#include <stdio.h>
#include <signal.h>

void
nh(int s,siginfo_t *si,void *sc) {
  printf("%p\n",si->si_addr);
  exit(0);
}

int
main() {

  struct sigaction sa;
  char c[3];

  memset(&sa,0,sizeof(sa));
  sa.sa_sigaction=nh;
  sa.sa_flags=SA_RESTART|SA_SIGINFO;
  sigaction(SIGSEGV,&sa,0);
  c[4096]=0;

/*    raise(SIGSEGV); */

  return 0;

}
=============================================================================
camm@kullervo:~$ cc -g q.c -o q 
cc -g q.c -o q 
camm@kullervo:~$ ./q
./q
(nil)
=============================================================================
Take care,

-- 
Camm Maguire			     			camm@enhanced.com
==========================================================================
"The earth is but one country, and mankind its citizens."  --  Baha'u'llah

             reply	other threads:[~2001-03-08 22:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-08 22:27 Camm Maguire [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-03-09  0:26 2.2.x kernels not filling in siginfo_t.si_addr on SEGV? David Watson
2001-03-09  3:28 ` Camm Maguire
     [not found]   ` <20010309083035.A27596@flint.arm.linux.org.uk>
2001-03-09 22:29     ` Camm Maguire

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=E14b8sw-0007A2-00@intech19.enhanced.com \
    --to=camm@enhanced.com \
    --cc=linux-kernel@vger.kernel.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