From: tracemein@gmail.com (Naren)
Subject: [ltt-dev] UST - Problems in recording trace on a current process
Date: Tue, 9 Feb 2010 18:11:33 +0100 [thread overview]
Message-ID: <19fa8ef31002090911x67b99823v54f0e423ff6ea121@mail.gmail.com> (raw)
In-Reply-To: <201002091142.33606.pierre-marc.fournier@polymtl.ca>
Hi Pierre
I did a strace on ustctl as suggested by you. Found this problem with
connect call in strace.
*socket(PF_FILE, SOCK_STREAM, 0) = 3*
*connect(3, {sa_family=AF_FILE, path="/tmp/ust-app-socks/11191"}, 110) = -1
ENOENT (No such file or directory)*
*gettid() = 23476*
I did a manual check on ust-app-socks, found only "ustd" running inside
that.
Regards,
Naren
On Tue, Feb 9, 2010 at 5:42 PM, Pierre-Marc Fournier <
pierre-marc.fournier at polymtl.ca> wrote:
> On February 8, 2010 20:48:16 soumyakanti chakraborty wrote:
> > Hi Pierre
> >
> > I am still getting the same errors during the tracing of a particular
> > process with specific pid's -
> >
> > *ustctl[1605/1605]: Error: connect: No such file or directory (in
> > ustcomm_connect_path() at ../libustcomm/ustcomm.c:452)*
> > *ustcmd_send_cmd: could not connect to PID 1283*
> > *error while trying to list markers for PID 1283*
> >
>
> Further thoughts on this. You could see this message also if libust is not
> linked to the program you are trying to trace.
>
> Another case is if your program is registering a handler for SIGUSR1.
>
> If not, send us the strace output around the connect() call.
>
> pmf
>
> _______________________________________________
> ltt-dev mailing list
> ltt-dev at lists.casi.polymtl.ca
> http://lists.casi.polymtl.ca/cgi-bin/mailman/listinfo/ltt-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.casi.polymtl.ca/pipermail/lttng-dev/attachments/20100209/b3920165/attachment-0003.htm>
WARNING: multiple messages have this Message-ID
From: tracemein@gmail.com (Naren)
Subject: [ltt-dev] UST - Problems in recording trace on a current process
Date: Tue, 9 Feb 2010 18:11:33 +0100 [thread overview]
Message-ID: <19fa8ef31002090911x67b99823v54f0e423ff6ea121@mail.gmail.com> (raw)
Message-ID: <20100209171133.tSPz1KZdslOoOsWrbqkTRH-XcOBvL7mKE9Lp-cCEZIc@z> (raw)
In-Reply-To: <201002091142.33606.pierre-marc.fournier@polymtl.ca>
Hi Pierre
I did a strace on ustctl as suggested by you. Found this problem with
connect call in strace.
*socket(PF_FILE, SOCK_STREAM, 0) = 3*
*connect(3, {sa_family=AF_FILE, path="/tmp/ust-app-socks/11191"}, 110) = -1
ENOENT (No such file or directory)*
*gettid() = 23476*
I did a manual check on ust-app-socks, found only "ustd" running inside
that.
Regards,
Naren
On Tue, Feb 9, 2010 at 5:42 PM, Pierre-Marc Fournier <
pierre-marc.fournier at polymtl.ca> wrote:
> On February 8, 2010 20:48:16 soumyakanti chakraborty wrote:
> > Hi Pierre
> >
> > I am still getting the same errors during the tracing of a particular
> > process with specific pid's -
> >
> > *ustctl[1605/1605]: Error: connect: No such file or directory (in
> > ustcomm_connect_path() at ../libustcomm/ustcomm.c:452)*
> > *ustcmd_send_cmd: could not connect to PID 1283*
> > *error while trying to list markers for PID 1283*
> >
>
> Further thoughts on this. You could see this message also if libust is not
> linked to the program you are trying to trace.
>
> Another case is if your program is registering a handler for SIGUSR1.
>
> If not, send us the strace output around the connect() call.
>
> pmf
>
> _______________________________________________
> ltt-dev mailing list
> ltt-dev at lists.casi.polymtl.ca
> http://lists.casi.polymtl.ca/cgi-bin/mailman/listinfo/ltt-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.casi.polymtl.ca/pipermail/lttng-dev/attachments/20100209/b3920165/attachment-0002.htm>
next prev parent reply other threads:[~2010-02-09 17:11 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 [this message]
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
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=19fa8ef31002090911x67b99823v54f0e423ff6ea121@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