public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/13486] New: pass-4 error (frame_base undeclared), inlined function argument
Date: Thu, 08 Dec 2011 20:15:00 -0000	[thread overview]
Message-ID: <bug-13486-6586@http.sourceware.org/bugzilla/> (raw)

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

             Bug #: 13486
           Summary: pass-4 error (frame_base undeclared), inlined function
                    argument
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: translator
        AssignedTo: systemtap@sourceware.org
        ReportedBy: fche@redhat.com
    Classification: Unclassified


Created attachment 6098
  --> http://sourceware.org/bugzilla/attachment.cgi?id=6098
rmap.o from build tree

On a rawhide VM, the following script causes buggy loc2c code generation:


% stap -p4 -e 'probe kernel.function("try_to_unmap_cluster")
{println($mapcount)}' 
/var/tmp/stapEaoDzl/stap_18fc171ff2ff11b32cb9f4b595ad29e1_1254.c: In function
‘function__dwarf_tvar_get_mapcount_0’:
/var/tmp/stapEaoDzl/stap_18fc171ff2ff11b32cb9f4b595ad29e1_1254.c:175:16: error:
‘frame_base’ undeclared (first use in this function)
/var/tmp/stapEaoDzl/stap_18fc171ff2ff11b32cb9f4b595ad29e1_1254.c:175:16: note:
each undeclared identifier is reported only once for each function it appears
in
make[1]: *** [/var/tmp/stapEaoDzl/stap_18fc171ff2ff11b32cb9f4b595ad29e1_1254.o]
Error 1
make: *** [_module_/var/tmp/stapEaoDzl] Error 2

% dmesg|head

[    0.000000] Linux version 3.2.0-rc4-next-20111205 (fche@vm-rawhide-64) (gcc
version 4.6.2 20111027 (Red Hat 4.6.2-1) (GCC) ) #1 SMP Mon Dec 5 05:30:40 EST
2011

% readelf -w /notnfs/linux-2.6/mm/rmap.o

[...]
    <e6ac>   DW_AT_name        : (indirect string, offset: 0x1220):
try_to_unmap_cluster

    <e6b0>   DW_AT_decl_file   : 1      
    <e6b1>   DW_AT_decl_line   : 1315   
    <e6b3>   DW_AT_prototyped  : 1      
    <e6b3>   DW_AT_type        : <0x7c> 
    <e6b7>   DW_AT_inline      : 1      (inlined)
    <e6b8>   DW_AT_sibling     : <0xe796>       
 <2><e6bc>: Abbrev Number: 71 (DW_TAG_formal_parameter)
    <e6bd>   DW_AT_name        : (indirect string, offset: 0x30e9): cursor      
    <e6c1>   DW_AT_decl_file   : 1      
    <e6c2>   DW_AT_decl_line   : 1315   
    <e6c4>   DW_AT_type        : <0x11a>        
 <2><e6c8>: Abbrev Number: 71 (DW_TAG_formal_parameter)
    <e6c9>   DW_AT_name        : (indirect string, offset: 0x3fa5): mapcount    
    <e6cd>   DW_AT_decl_file   : 1      
    <e6ce>   DW_AT_decl_line   : 1315   
    <e6d0>   DW_AT_type        : <0xf1b>        
 <2><e6d4>: Abbrev Number: 64 (DW_TAG_formal_parameter)
    <e6d5>   DW_AT_name        : vma    
    <e6d9>   DW_AT_decl_file   : 1      
    <e6da>   DW_AT_decl_line   : 1316   
    <e6dc>   DW_AT_type        : <0x4d83>       

I don't see a location list for this "mapcount" variable, but that must just be 
my lyin' eyes.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

             reply	other threads:[~2011-12-08 20:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-08 20:15 fche at redhat dot com [this message]
2011-12-08 21:22 ` [Bug translator/13486] " fche at redhat dot com
2012-09-27  0:57 ` jistone at redhat dot com
2012-09-27  8:07 ` mjw at redhat dot com
2012-09-27 16:53 ` jistone at redhat dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-13486-6586@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=systemtap@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).