This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: [BUG] syscall.unlink no longer works after upgrading kernel to 3.7.3
- From: Mark Wielaard <mjw at redhat dot com>
- To: Josh Stone <jistone at redhat dot com>
- Cc: Zheng Da <zhengda1936 at gmail dot com>, agentzh <agentzh at gmail dot com>, "systemtap at sourceware dot org" <systemtap at sourceware dot org>
- Date: Tue, 28 May 2013 22:32:23 +0200
- Subject: Re: [BUG] syscall.unlink no longer works after upgrading kernel to 3.7.3
- References: <CAB4Tn6PdW3GOa09z_tfjQs=F+7XLOqMr5+c5GourX5e0v8FMeQ at mail dot gmail dot com> <1360054656 dot 3837 dot 13 dot camel at bordewijk dot wildebeest dot org> <51114188 dot 60400 at redhat dot com> <CAFLer83DQhCQg7Y3NKR0EUYePzp+fETDTeYEthUXKarAySM0_g at mail dot gmail dot com> <20130528191449 dot GA31042 at toonder dot wildebeest dot org> <CAFLer81NE1bocCbufPTtLLZ-pZz2kVA5r3rKoCgjmc_6w+fwng at mail dot gmail dot com> <51A511FD dot 8010006 at redhat dot com>
On Tue, May 28, 2013 at 01:22:21PM -0700, Josh Stone wrote:
> But there are other reasons for "not accessible" errors, as described in
> "man error::dwarf". Just optimization or inlining can be enough to make
> variables unavailable from certain addresses.
>
> Are you able to look at the DWARF dump to see where that variable can be
> reached?
See also http://sourceware.org/systemtap/wiki/TipContextVariables
for some hints and tips on tracking down what could be the real issue.