From: "Turgis, Frederic" <f-turgis@ti.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: Mark Wielaard <mjw@redhat.com>,
"systemtap@sourceware.org" <systemtap@sourceware.org>
Subject: RE: Making the transport layer more robust
Date: Tue, 30 Aug 2011 13:20:00 -0000 [thread overview]
Message-ID: <13872098A06B02418CF379A158C0F1460162EB569E@dnce02.ent.ti.com> (raw)
In-Reply-To: <y0m1uw4z35j.fsf@fche.csb>
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
>
next prev parent reply other threads:[~2011-08-30 13:20 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-19 8:59 Mark Wielaard
2011-07-19 11:42 ` Mark Wielaard
2011-07-19 15:03 ` Mark Wielaard
2011-07-20 8:29 ` Mark Wielaard
2011-07-19 15:05 ` William Cohen
2011-07-20 14:13 ` Mark Wielaard
2011-07-21 17:18 ` David Smith
2011-08-12 17:43 ` Mark Wielaard
2011-08-15 8:24 ` Mark Wielaard
2011-08-15 18:30 ` Josh Stone
2011-08-16 13:23 ` Mark Wielaard
2011-08-25 12:12 ` Turgis, Frederic
2011-08-26 15:45 ` Turgis, Frederic
2011-08-26 18:45 ` Frank Ch. Eigler
2011-08-29 8:32 ` Turgis, Frederic
2011-08-29 11:21 ` Frank Ch. Eigler
2011-08-29 14:46 ` Frank Ch. Eigler
2011-08-30 13:20 ` Turgis, Frederic [this message]
2011-09-05 11:27 ` Mark Wielaard
2011-09-05 14:32 ` Turgis, Frederic
[not found] ` <13872098A06B02418CF379A158C0F1460163182604@dnce02.ent.ti.com>
2011-09-06 10:12 ` Mark Wielaard
2011-09-06 14:30 ` Turgis, Frederic
2011-09-06 14:37 ` David Smith
2011-09-06 15:37 ` David Smith
2011-09-06 16:25 ` Turgis, Frederic
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=13872098A06B02418CF379A158C0F1460162EB569E@dnce02.ent.ti.com \
--to=f-turgis@ti.com \
--cc=fche@redhat.com \
--cc=mjw@redhat.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).