This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug translator/15587] New: Line numbers are missing/incorrect for inline statements
- From: "jistone at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sourceware dot org
- Date: Wed, 05 Jun 2013 19:55:20 +0000
- Subject: [Bug translator/15587] New: Line numbers are missing/incorrect for inline statements
- Auto-submitted: auto-generated
http://sourceware.org/bugzilla/show_bug.cgi?id=15587
Bug ID: 15587
Summary: Line numbers are missing/incorrect for inline
statements
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: translator
Assignee: systemtap at sourceware dot org
Reporter: jistone at redhat dot com
First, notice how a non-inline function behaves:
$ stap -l 'kernel.function("do_sys_open@fs/open.c").*'
kernel.function("do_sys_open@fs/open.c:960").call
kernel.function("do_sys_open@fs/open.c:960").exported
kernel.function("do_sys_open@fs/open.c:960").return
$ stap -l 'kernel.statement("do_sys_open@fs/open.c:*")'
kernel.statement("do_sys_open@fs/open.c:961")
kernel.statement("do_sys_open@fs/open.c:965")
kernel.statement("do_sys_open@fs/open.c:973")
kernel.statement("do_sys_open@fs/open.c:976")
kernel.statement("do_sys_open@fs/open.c:979")
kernel.statement("do_sys_open@fs/open.c:981")
Now compare to an inlined function:
$ stap -l 'kernel.function("__get_file_write_access@fs/open.c").*'
kernel.function("__get_file_write_access@fs/open.c:656").inline
$ stap -l 'kernel.statement("__get_file_write_access@fs/open.c:*")'
kernel.statement("__get_file_write_access@fs/open.c")
The line number is absent, so we don't know what locations it actually found.
And in fact, there could be multiple locations, with different $var
availability, but listing mode will only show it once since the pn() is the
same.
--
You are receiving this mail because:
You are the assignee for the bug.