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]

[Bug translator/15688] New: Accessing globals in DSO or PIE results in read faults


http://sourceware.org/bugzilla/show_bug.cgi?id=15688

            Bug ID: 15688
           Summary: Accessing globals in DSO or PIE results in read faults
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: translator
          Assignee: systemtap at sourceware dot org
          Reporter: agentzh at gmail dot com

I've noticed that use of @var("foo") or $foo in either probe process.function
or probe process.mark could lead to the following error when there is a global
variable named "foo" in the current userspace DSO or PIE module:

  ERROR: read fault [man error::fault] at 0x          (null) (addr) near
operator '@var'

It seems that dwarf_var_expanding_visitor::visit_target_symbol can resolve the
variable into a global variable but does not enable the VMA tracker for the
current module accordingly.

I can always reproduce this with trivial example on the current master (commit
5883b785fa)

-- 
You are receiving this mail because:
You are the assignee for the bug.


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