From: David Ahern <dsahern@gmail.com>
To: Dongsoo Nathaniel Kim <dongsoo.kim@gmail.com>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: perf terminates immediately with segfault in dmesg
Date: Wed, 27 Feb 2013 09:17:07 -0700 [thread overview]
Message-ID: <512E3183.6000007@gmail.com> (raw)
In-Reply-To: <CAP+Vy9d8Yd7HoxvixS6oT+wow+rV2PzriKBqOw17VVFwTc0iNg@mail.gmail.com>
On 2/27/13 7:21 AM, Dongsoo Nathaniel Kim wrote:
> Hi,
>
> I'm trying to profile kvm guest and host as well.
> I checked out v3.8 vanilla kernel and built bundled perf tool.
> (commit 19f949f52599ba7c3f67a5897ac6be14bfcb1200)
>
> Here is my command line:
> sudo perf kvm --host --guest --guestmount=/tmp/guestmount record -o
> my.perf.data
> (I mounted guest instance on /tmp/guestmount using sshfs)
>
> and perf gets terminated immediately and no clue but segfault message in
> dmesg:
> [11618.130483] perf[39937]: segfault at 30 ip 00007fed26de1121 sp
> 00007fff0394c258 error 4 in libc-2.15.so[7fed26d58000+1b5000]
>
> Any idea? Can too many processor core cause this problem?
Does this solve the problem for you?
diff --git a/tools/perf/builtin-kvm.c b/tools/perf/builtin-kvm.c
index ca3f80e..e55701d 100644
--- a/tools/perf/builtin-kvm.c
+++ b/tools/perf/builtin-kvm.c
@@ -973,7 +973,7 @@ __cmd_buildid_list(const char *file_name, int argc,
const char **argv)
int cmd_kvm(int argc, const char **argv, const char *prefix
__maybe_unused)
{
- const char *file_name;
+ const char *file_name = NULL;
const struct option kvm_options[] = {
OPT_STRING('i', "input", &file_name, "file",
next prev parent reply other threads:[~2013-02-27 16:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-27 14:21 perf terminates immediately with segfault in dmesg Dongsoo Nathaniel Kim
2013-02-27 16:17 ` David Ahern [this message]
2013-02-28 1:22 ` Dongsoo Nathaniel Kim
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=512E3183.6000007@gmail.com \
--to=dsahern@gmail.com \
--cc=dongsoo.kim@gmail.com \
--cc=linux-perf-users@vger.kernel.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 NNTP newsgroup(s).