This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug translator/2438] Can't resolve $fd argument for sys_readv and sys_writev on ppc64
- From: "aoliva at sourceware dot org" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sources dot redhat dot com
- Date: 15 Apr 2006 05:45:05 -0000
- Subject: [Bug translator/2438] Can't resolve $fd argument for sys_readv and sys_writev on ppc64
- References: <20060309040316.2438.hien@us.ibm.com>
- Reply-to: sourceware-bugzilla at sourceware dot org
------- 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.