From: fche@redhat.com (Frank Ch. Eigler)
To: Martin Martin <martin@infinio.com>
Cc: "Yichun Zhang (agentzh)" <agentzh@gmail.com>, systemtap@sourceware.org
Subject: Re: How do I trap the return of a function in a user space process?
Date: Sat, 07 Sep 2013 00:42:00 -0000 [thread overview]
Message-ID: <y0mppslec1l.fsf@fche.csb> (raw)
In-Reply-To: <CAAQ0mPgQs59g7DCUZEeViKJJZKLuua4ErrBYLVc0-RMKp6xMWw@mail.gmail.com> (Martin Martin's message of "Fri, 6 Sep 2013 12:35:13 -0400")
Martin Martin <martin@infinio.com> writes:
> I manged to solve this problem: I was compiling with clang++.
> Switching to g++ caused all my functions to show up.
Can clang++ generate DWARF data? It'd be interesting to
see a sample binary that stap cannot deal with.
- FChE
next prev parent reply other threads:[~2013-09-07 0:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-05 20:36 Martin Martin
2013-09-05 20:42 ` Yichun Zhang (agentzh)
2013-09-06 14:17 ` Martin Martin
2013-09-06 15:57 ` Martin Martin
2013-09-06 16:35 ` Martin Martin
2013-09-07 0:42 ` Frank Ch. Eigler [this message]
2013-09-09 12:23 ` Martin Martin
2013-09-09 18:13 ` Mark Wielaard
2013-09-09 18:32 ` Josh Stone
2013-09-09 19:29 ` Mark Wielaard
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=y0mppslec1l.fsf@fche.csb \
--to=fche@redhat.com \
--cc=agentzh@gmail.com \
--cc=martin@infinio.com \
--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).