public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "aoliva at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug translator/2438] Can't resolve $fd argument for sys_readv and sys_writev on ppc64
Date: Sat, 15 Apr 2006 05:45:00 -0000	[thread overview]
Message-ID: <20060415054505.326.qmail@sourceware.org> (raw)
In-Reply-To: <20060309040316.2438.hien@us.ibm.com>


------- Additional Comments From aoliva at sourceware dot org  2006-04-15 05:45 -------
What does the debug info for these functions look like?  I suspect this may be
fixed in U4, with the backport of variable tracking and location lists for
variables, but I don't have easy access to a RHEL4 U3 ppc64 box to compare with
it.  Also, I don't know whether stap actually supports location lists.  Here's
what I get from readelf -w, using GCC trunk:

 <1><70df3d>: Abbrev Number: 78 (DW_TAG_subprogram)
     DW_AT_external    : 1
     DW_AT_name        : (indirect string, offset: 0x41d64): sys_readv
     DW_AT_decl_file   : 1
     DW_AT_decl_line   : 601
     DW_AT_prototyped  : 1
     DW_AT_type        : <70440b>
     DW_AT_low_pc      : 0xc0000000000c783c
     DW_AT_high_pc     : 0xc0000000000c7900
     DW_AT_frame_base  : 0x111a7c       (location list)
     DW_AT_sibling     : <70e01a>
 <2><70df63>: Abbrev Number: 67 (DW_TAG_formal_parameter)
     DW_AT_name        : fd
     DW_AT_decl_file   : 1
     DW_AT_decl_line   : 600
     DW_AT_type        : <704124>
     DW_AT_location    : 0x111ab4       (location list)

    00111ab4 c0000000000c783c c0000000000c784c (DW_OP_reg3)
    00111ab4 c0000000000c7850 c0000000000c7868 (DW_OP_reg3)
    00111ab4 <End of list>

RHEL4 U4's GCC generates equivalent debug info.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |aoliva at sourceware dot org
             Status|NEW                         |WAITING


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

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

  reply	other threads:[~2006-04-15  5:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-09  4:03 [Bug translator/2438] New: " hien at us dot ibm dot com
2006-04-15  5:45 ` aoliva at sourceware dot org [this message]
2006-04-24  9:07 ` [Bug translator/2438] " guij at cn dot ibm dot com
2006-04-24  9:08 ` guij at cn dot ibm dot com
2006-04-26  6:19 ` guij at cn dot ibm dot com
2006-05-08 15:17 ` fche at redhat dot com
2006-05-09  1:48 ` guij at cn dot ibm dot com
2006-05-09 19:26 ` fche at redhat dot com
2006-05-23  5:39 ` aoliva at sourceware dot org
2006-05-23 12:49 ` fche at redhat dot com
2006-05-23 23:59 ` aoliva at sourceware dot org
2007-05-08 18:51 ` fche 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=20060415054505.326.qmail@sourceware.org \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=systemtap@sources.redhat.com \
    /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).