From: Gaurav Dhiman <dimanuec@gmail.com>
To: Srikar Dronamraju <srikar@linux.vnet.ibm.com>, systemtap@sourceware.org
Subject: Re: Segmentation Fault: Task died at uprobe probepoint
Date: Tue, 15 Jun 2010 09:11:00 -0000 [thread overview]
Message-ID: <AANLkTikm8mEPjxO8EDvzBEbrSZRSu7vs1kLZOu9WjBs1@mail.gmail.com> (raw)
In-Reply-To: <AANLkTilvvj9hdiaa9VWjO0j-jK02LMweg5cAEBgoLyRK@mail.gmail.com>
On Mon, Jun 14, 2010 at 12:00 AM, Srikar Dronamraju
<srikar@linux.vnet.ibm.com> wrote:
>> The uprobe-test code is as follows:
>>
>> int test_func(int i)
>> {
>> printf("%d\n", i);
>> return j;
> ^^^^^
> Guess you meant "return i;"
Yes, I meant 'i' :)
>> Then I ran the script as root using stap -v test.stp; it is compiled
>> and inserted successfully. I see the following message if I do dmesg:
>> [ 1694.148460] stap_9736f2321b446f9fc03126194f89aac2_1643: systemtap:
>> 1.2/0.131, base: ffffffffa0010000, memory
>> 136data/29text/10ctx/13net/34alloc kb, probes: 2
>
> Looks to me that you are using a pretty recent systemtap with a pretty
> old elfutils. Is is possible to try building systemtap with a later
> version of elfutils?
>
I have version 0.13a installed on my system. Is that too old? I can
give it a shot with latter versions.
>> However, when i actually run uprobe-test, although both the probes
>> fire successfully, the task generates a segmentation fault and dies on
>> the 'test_func' probe. I see the following message on doing dmesg:
>
>> [ 1709.650827] Task died at uprobe probepoint: pid/tgid = 3934/3934,
>> probepoint = 0x400517
>
>
> This means that the process died before the uprobe operation completed.
> i.e either it was still running the handler or singlestep operation
> hadnt occurred.
> - Did you try using the core with gdb? Does address in bt and
> disassemble output of test_func show the same address?
Actually the uprobe is firing. I see the output of the following
probe, when the function gets called:
probe process("/home/gdhiman/tests/uprobe-test").function("test_func")
{
printf("test_func called!\n");
log($$parms);
}
However, the program immediately dies. The address of the function is
0x400517, the same as that shown in the probepoint.
>
> I am not able to see this problem. (I am running on a different kernel)
>
Which versions (systemtap and kernel) are you using? I might give them
a shot as well.
Thanks,
-Gaurav
next prev parent reply other threads:[~2010-06-15 0:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-14 9:18 Gaurav Dhiman
2010-06-14 12:55 ` Srikar Dronamraju
[not found] ` <AANLkTilvvj9hdiaa9VWjO0j-jK02LMweg5cAEBgoLyRK@mail.gmail.com>
2010-06-15 9:11 ` Gaurav Dhiman [this message]
2010-06-15 17:46 ` Mark Wielaard
2010-06-16 13:54 ` Gaurav Dhiman
2010-06-16 19:05 ` Frank Ch. Eigler
2010-06-22 8:57 ` Gaurav Dhiman
2010-06-22 10:36 ` Roland McGrath
2010-06-22 13:05 ` Gaurav Dhiman
2010-06-22 13:11 ` Roland McGrath
2010-06-22 13:12 ` Gaurav Dhiman
2010-06-15 18:17 ` Srikar Dronamraju
2010-06-16 14:19 ` Gaurav Dhiman
2010-06-14 21:06 ` Frank Ch. Eigler
2010-06-15 9:24 ` Gaurav Dhiman
2010-06-15 10:39 ` Frank Ch. Eigler
2010-06-15 12:25 ` Gaurav Dhiman
2010-06-15 18:07 ` Mark Wielaard
2010-06-16 14:08 ` Gaurav Dhiman
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=AANLkTikm8mEPjxO8EDvzBEbrSZRSu7vs1kLZOu9WjBs1@mail.gmail.com \
--to=dimanuec@gmail.com \
--cc=srikar@linux.vnet.ibm.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).