This is the mail archive of the systemtap@sourceware.org mailing list for the systemtap project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: kprobe fault handling

From: Martin Hunt <hunt at redhat dot com>
To: Jim Keniston <jkenisto at us dot ibm dot com>
Cc: prasanna at in dot ibm dot com, Richard J Moore <richardj_moore at uk dot ibm dot com>, suparna at in dot ibm dot com, "systemtap at sources dot redhat dot com" <systemtap at sources dot redhat dot com>
Date: Thu, 09 Feb 2006 21:40:26 -0800
Subject: Re: kprobe fault handling
Organization: Red Hat Inc
References: <20060208043831.GA9313@in.ibm.com> <OFD9B8CED9.AB543156-ON8025710F.003BD103-8025710F.003EFA68@uk.ibm.com> <20060209072338.GA2902@in.ibm.com> <1139520938.2779.171.camel@dyn9047018079.beaverton.ibm.com> <1139522818.4127.15.camel@monkey2>

Maybe I should post one of my test programs. The attached one crashes on
my i686 system running an SMP kernel in a couple of seconds. On non-SMP
kernels, it prints a bunch of junk to syslog but doesn't seem to crash,
although I haven't tested it much.  With my simple fixup_exception patch
to the handler, it runs perfectly. I've modified it to keep looping
through the address space and run it for hours.

Attachment: mem_test.stp
Description: Text document

Follow-Ups:
- Re: kprobe fault handling
  - From: Frank Ch. Eigler

References:
- Re: kprobe fault handling
  - From: Suparna Bhattacharya
- Re: kprobe fault handling
  - From: Richard J Moore
- Re: kprobe fault handling
  - From: Prasanna S Panchamukhi
- Re: kprobe fault handling
  - From: Jim Keniston
- Re: kprobe fault handling
  - From: Martin Hunt

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]