This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: semantic error: not accessible at this address
- From: "Frank Ch. Eigler" <fche at redhat dot com>
- To: Vincent Bernat <bernat at luffy dot cx>
- Cc: systemtap at sourceware dot org
- Date: Fri, 27 Sep 2013 20:02:47 -0400
- Subject: Re: semantic error: not accessible at this address
- Authentication-results: sourceware.org; auth=none
- References: <87ioxmf2e9 dot fsf at guybrush dot luffy dot cx> <y0mvc1mt0k7 dot fsf at fche dot csb> <8738opg9ym dot fsf at guybrush dot luffy dot cx> <20130927230432 dot GA32221 at redhat dot com> <87wqm1etsz dot fsf at guybrush dot luffy dot cx> <20130927232529 dot GB32221 at redhat dot com> <87pprtesfe dot fsf at guybrush dot luffy dot cx>
Hi -
> > The -mfentry-compensation code should cause you to be seeing some
> > messages like this:
> >
> > retrying variable location-list lookup at address pc+5
>
> OK
Yup, the entry below confirms it:
> >> [...]
> 005ec5ff ffffffff811b42b5 ffffffff811b42eb (DW_OP_reg5 (rdi))
> 005ec5ff ffffffff811b42eb ffffffff811b43e8 (DW_OP_reg3 (rbx))
> 005ec5ff ffffffff811b43fa ffffffff811b44a9 (DW_OP_reg3 (rbx))
> 005ec5ff <End of list>
Your vfs_write starts at 0xffffffff811b42b0, and "file" comes into scope
five bytes later. This is the PR15123 scenario. Does your environment
by any chance include $PR15123_DISABLE? If so, unset that. If not,
maybe it's time to debug dwflpp.cxx:translate_location, line 2411-ish.
- FChE