From: Zoltan Kiss <zoltan.kiss@linaro.org>
To: systemtap@sourceware.org
Subject: process().statement() doesn't seem to work
Date: Fri, 26 Jun 2015 18:58:00 -0000 [thread overview]
Message-ID: <558DA0E3.9060904@linaro.org> (raw)
Hi,
I want to use systemtap to figure out the local variables in a function
where something goes fishy. The function's code is here:
http://dpdk.org/browse/dpdk/tree/lib/librte_pmd_ixgbe/ixgbe_rxtx.c?id=v1.7.1#n1313
It's a receive function of DPDK's userspace poll mode driver, so it's
called in an infinite loop. When I try this, it appers to work:
probe
process("/usr/sbin/ovs-vswitchd").function("ixgbe_recv_scattered_pkts").return
{
log($$locals)
exit();
}
The output is:
rxq=0x7fff852ee000 rx_ring=? rxdp=? sw_ring=? rxe=? first_seg=?
last_seg=? rxm=? nmb=? rxd={...} dma=? staterr=? hlen_type_rss=? rx_id=?
nb_rx=0x0 nb_hold=0x0 data_len=? pkt_flags=?
But it doesn't show most of the variables I need. It returns nb_rx=0, so
I know where are the two points where things can go wrong, but I can't
see the output of those variables (staterr and nmb)
When I try to define the probe as this:
probe
process("/usr/sbin/ovs-vswitchd").statement("*@lib/librte_pmd_ixgbe/ixgbe_rxtx.c:1359")
Or with any line number inside that function, the probe is never
reached. I'm using gcc 4.8.4, DPDK is statically linked to my application.
Does anyone have an idea what might went wrong?
Regards,
Zoltan Kiss
next reply other threads:[~2015-06-26 18:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-26 18:58 Zoltan Kiss [this message]
2015-06-29 23:39 ` Josh Stone
2015-07-09 14:49 ` Frank Ch. Eigler
2015-07-10 22:59 ` Josh Stone
2015-07-20 17:54 ` Zoltan Kiss
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=558DA0E3.9060904@linaro.org \
--to=zoltan.kiss@linaro.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).