[ltt-dev] UST - Problems in recording trace on a current process

[Pierre-Marc Fournier]

On February 9, 2010 12:11:33 Naren wrote:
> 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.

Ok, good progress here.

Can you check that:
- the program you want to trace has been linked dynamically against libust. 
You can do so with the ldd tool.
- you did a "make install" when you upgraded your ust. You would get this 
error if ustctl and your traced program were linked against different 
versions of libust.so.
- there are no error messages in the console where your traced program is 
running.

>
> 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