From: tracemein@gmail.com (Naren)
Subject: [ltt-dev] UST - Problems in recording trace on a current process
Date: Wed, 10 Feb 2010 17:53:12 +0100 [thread overview]
Message-ID: <19fa8ef31002100853n189221f3u3015c85afc65db5c@mail.gmail.com> (raw)
Message-ID: <20100210165312.UtZfFFbToIPsYwuzE__PtnkgC5GYF4uRgqiunS26CpE@z> (raw)
In-Reply-To: <4B72D009.2060702@polymtl.ca>
Hi Pierre
>>I'm not sure what you could have done that would necessitate a clean
>>install. If you suspect your installation is dirty or composed of libs
>>of mixed versions, I suggest to do clean install as the situation can
>>result in segfaults.
>>
>>But you might face a real bug. Based on the strace output, it is ustctl
>>that is segfaulting. Could you compile it with:
>>
>>make clean
>>CFLAGS="-g3" ./configure
>>make
>>make install
>>
>>Then run the same ustctl command within gdb and post the backtrace (bt
>>command) you get after the segfault.
As suggested, I did a back trace on ustctl. Prior to that, i did a clean
install and configured ust with flags on. Here is the stackdump produced by
bt.
*(gdb) bt full*
*#0 0x0804ddef in ustcmd_get_cmsf (cmsf=0xbffff35c, pid=5189)*
* at ../libustcmd/ustcmd.c:284*
* state = 49 '1'*
* big_str = 0x8052018 "marker: metadata/core_marker_format 1
\"channel %s name %s format %s\" 0xb7ee3c6a\nmarker:
metadata/core_marker_format 1 \"channel %s name %s format %s\"
0xb7ee4bb0\nmarker: metadata/core_marker_id 1 \"chann"...*
* result = 0*
* tmp_cmsf = 0x8052408*
* i = 135144*
* cmsf_ind = 13*
*#1 0x08049cff in main (argc=3, argv=0xbffff534) at ustctl.c:267*
* i = 0*
* pidit = 0x8052008*
* result = 0*
* opts = {cmd = LIST_MARKERS, pids = 0x8052008, regex = 0x0}*
* cmsf = 0x0*
* __func__ = "main"*
*(gdb) *
Regards,
Naren
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.casi.polymtl.ca/pipermail/lttng-dev/attachments/20100210/cfb05e6a/attachment-0003.htm>
next prev parent reply other threads:[~2010-02-10 16:53 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-08 21:49 Naren
2010-02-08 21:49 ` Naren
2010-02-08 22:19 ` Pierre-Marc Fournier
[not found] ` <19fa8ef31002081428x1e215acfgd81d505ee359ce9@mail.gmail.com>
[not found] ` <201002081744.06912.pierre-marc.fournier@polymtl.ca>
2010-02-08 23:54 ` Naren
2010-02-08 23:54 ` Naren
2010-02-09 1:37 ` soumyakanti chakraborty
2010-02-09 1:37 ` soumyakanti chakraborty
2010-02-09 1:48 ` soumyakanti chakraborty
2010-02-09 1:48 ` soumyakanti chakraborty
2010-02-09 5:45 ` Pierre-Marc Fournier
2010-02-09 14:44 ` Naren
2010-02-09 14:44 ` Naren
2010-02-09 14:51 ` Douglas Santos
2010-02-09 14:51 ` Douglas Santos
2010-02-09 16:43 ` Naren
2010-02-09 16:43 ` Naren
2010-02-09 17:11 ` Pierre-Marc Fournier
2010-02-09 16:42 ` Pierre-Marc Fournier
2010-02-09 17:11 ` Naren
2010-02-09 17:11 ` Naren
2010-02-09 17:25 ` Pierre-Marc Fournier
2010-02-09 20:40 ` Naren
2010-02-09 20:40 ` Naren
2010-02-09 21:25 ` Douglas Santos
2010-02-09 21:28 ` Pierre-Marc Fournier
2010-02-10 0:50 ` Naren
2010-02-10 0:50 ` Naren
2010-02-10 15:26 ` Pierre-Marc Fournier
2010-02-10 16:53 ` Naren [this message]
2010-02-10 16:53 ` Naren
2010-02-10 20:15 ` Pierre-Marc Fournier
2010-02-10 22:08 ` Naren
2010-02-10 22:08 ` Naren
2010-02-12 0:18 ` Pierre-Marc Fournier
2010-02-12 9:10 ` Naren
2010-02-12 9:10 ` Naren
2010-02-15 6:04 ` Pierre-Marc Fournier
2010-02-15 6:23 ` Naveh, Ido
2010-02-15 12:16 ` Mathieu Desnoyers
2010-02-15 11:42 ` Naren
2010-02-15 11:42 ` Naren
2010-02-15 14:53 ` Pierre-Marc Fournier
2010-02-18 17:47 ` Pierre-Marc Fournier
2010-02-18 22:58 ` Naren
2010-02-18 22:58 ` Naren
2010-02-18 22:58 ` Naren
2010-02-19 16:50 ` Pierre-Marc Fournier
2010-02-19 17:15 ` Naren
2010-02-19 17:15 ` Naren
2010-02-19 17:15 ` Naren
2010-02-22 0:46 ` soumyakanti chakraborty
2010-02-22 0:46 ` soumyakanti chakraborty
2010-02-22 0:46 ` soumyakanti chakraborty
2010-02-23 15:15 ` Pierre-Marc Fournier
2010-02-26 1:55 ` soumyakanti chakraborty
2010-02-26 1:55 ` soumyakanti chakraborty
2010-02-26 1:55 ` soumyakanti chakraborty
2010-02-26 5:35 ` Pierre-Marc Fournier
2010-02-09 14:46 ` Douglas Santos
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=19fa8ef31002100853n189221f3u3015c85afc65db5c@mail.gmail.com \
--to=tracemein@gmail.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