From: "jistone at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug tapsets/10467] New: Failure in source:line matching aborts further searching
Date: Fri, 31 Jul 2009 01:45:00 -0000 [thread overview]
Message-ID: <20090731014526.10467.jistone@redhat.com> (raw)
I discovered this flaw when trying to use the fully-resolved name for a function
probe:
$ stap -l 'kernel.function("send_sigqueue")'
kernel.function("send_sigqueue@kernel/signal.c:1309")
$ stap -l 'kernel.function("send_sigqueue@kernel/signal.c:1309")' --vp 03
[...]
focused on module 'kernel'
selected source file 'arch/x86/kernel/signal.c'
semantic error: libdw failure (dwarf_getsrc_file): no matching address range
semantic error: no match while resolving probe point
kernel.function("send_sigqueue@kernel/signal.c:1309")
It matched arch/x86/kernel/signal.c because we implicitly use a '*/' in front of
source paths. The arch file is less than 1309 lines long though, so there can't
be any functions there.
However, instead of aborting, we should continue looking at other source files
so we can find the correct function in the plain 'kernel/signal.c'.
--
Summary: Failure in source:line matching aborts further searching
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: tapsets
AssignedTo: systemtap at sources dot redhat dot com
ReportedBy: jistone at redhat dot com
http://sourceware.org/bugzilla/show_bug.cgi?id=10467
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next reply other threads:[~2009-07-31 1:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-31 1:45 jistone at redhat dot com [this message]
2009-08-12 18:28 ` [Bug tapsets/10467] " 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=20090731014526.10467.jistone@redhat.com \
--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).