This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
RE: Making the transport layer more robust
Probably overkill but I opened http://sourceware.org/bugzilla/show_bug.cgi?id=13142 to track.
Using execlp has removed issue for other users so that's my favorite if OK for everyone.
Regards
Fred
Frederic Turgis
OMAP Platform Business Unit - OMAP System Engineering - Platform Enablement
>
Texas Instruments France SA, 821 Avenue Jack Kilby, 06270 Villeneuve Loubet. 036 420 040 R.C.S Antibes. Capital de EUR 753.920
-----Original Message-----
> From: Frank Ch. Eigler [mailto:fche@redhat.com]
> Sent: Monday, August 29, 2011 4:47 PM
> To: Turgis, Frederic
> Cc: Mark Wielaard; systemtap@sourceware.org
> Subject: Re: Making the transport layer more robust
>
>
> > I tested that Ok, as Android defines PATH correctly.
> However, I have
> > found these comments on a systemtap execvp call so I am no sure of
> > possible interferences with other requirements: [...]
>
> On second thought ... the place where we were worried about
> these extra syscalls is the path that fork/exec's the CMD
> part of "stap -c CMD". In the case of system_cmd() and
> cleanup_and_exit(), those don't matter.
>
> - FChE
>