[BUG] syscall.unlink no longer works after upgrading kernel to 3.7.3

[Mark Wielaard]

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.