mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Kevin B. Hendricks" <kevin.hendricks@sympatico.ca>
To: linux-kernel@vger.kernel.org
Cc: bero@arklinux.org
Subject: Re: Catching SIGSEGV with signal() in 2.6
Date: Mon, 5 Apr 2004 20:40:54 -0400	[thread overview]
Message-ID: <200404052040.54301.kevin.hendricks@sympatico.ca> (raw)

Hi,

Just in case this helps,  this is a simplified testcase of the OpenOffice.org 
code in question that always worked under 2.4 kernels on multiple 
architectures but fails on 2.6.X kernels on those same multiple platforms.

For some reason, the segfault generated by trying to write to address 0 can 
not be properly caught anymore (or at least it appears that way to me).

Hope this helps.

Kevin

[kbhend@base1 solar]$ cat testcase.c
#include <stdio.h>
#include <signal.h>
#include <setjmp.h>

typedef int (*TestFunc)( void* );
static jmp_buf check_env;
static int bSignal;

void SignalHdl( int sig )
{
  bSignal = 1;
  longjmp( check_env, sig );
}

int check( TestFunc func, void* p )
{
  int result;
  bSignal = 0;
  if ( !setjmp( check_env ) )
  {
        signal( SIGSEGV,        SignalHdl );
        signal( SIGBUS,         SignalHdl );
        result = func( p );
        signal( SIGSEGV,        SIG_DFL );
        signal( SIGBUS,         SIG_DFL );
  }
  if ( bSignal )
        return -1;
  else
        return 0;
}

int GetAtAddress( void* p )
{
  return *((char*)p);
}

int SetAtAddress( void* p )
{
  return *((char*)p)    = 0;
}

int CheckGetAccess( void* p )
{
  int b;
  b = -1 != check( (TestFunc)GetAtAddress, p );
  return b;
}

int CheckSetAccess( void* p )
{
  int b;
  b = -1 != check( (TestFunc)SetAtAddress, p );
  return b;
}

void InfoMemoryAccess( char* p )
{
  if ( CheckGetAccess( p ) )
    printf( "can read address %p\n", p );
  else
    printf( "can not read address %p\n", p );

  if ( CheckSetAccess( p ) )
    printf( "can write address %p\n", p );
  else
    printf( "can not write address %p\n", p );
}

int
main( int argc, char* argv[] )
{
  {
        char* p = NULL;
        InfoMemoryAccess( p );
        p = (char*)&p;
        InfoMemoryAccess( p );
  }
  exit( 0 );
}



             reply	other threads:[~2004-04-06  0:41 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-06  0:40 Kevin B. Hendricks [this message]
2004-04-06  2:04 ` Ulrich Drepper
2004-04-06  3:01   ` Kevin B. Hendricks
2004-04-06  4:08     ` Ulrich Drepper
2004-04-06 12:02       ` Kevin B. Hendricks
2004-04-06 15:53       ` Edgar Toernig
  -- strict thread matches above, loose matches on Subject: below --
2004-04-05 15:25 bero
2004-04-05 18:17 ` Jamie Lokier
2004-04-05 19:16   ` Chris Friesen
2004-04-05 20:40     ` Jamie Lokier
2004-04-05 20:59       ` Richard B. Johnson
2004-04-05 21:11         ` Chris Friesen
2004-04-05 21:12         ` Jamie Lokier
2004-04-05 21:23   ` bero

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=200404052040.54301.kevin.hendricks@sympatico.ca \
    --to=kevin.hendricks@sympatico.ca \
    --cc=bero@arklinux.org \
    --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

all inboxes | Powered by JetHome®