From: "eugen at debian dot org" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug runtime/9850] New: dtrace: Incorrect shell execution
Date: Mon, 16 Feb 2009 12:16:00 -0000 [thread overview]
Message-ID: <20090215212534.9850.eugen@debian.org> (raw)
dtrace -G uses shell to execute gcc:
call("gcc -fPIC -c " + fn + " -o " + filename, shell=True)
This makes directories with spaces problematic:
% mkdir a\ directory
% cd a\ directory
% touch test.d
% ../dtrace -G -s $PWD/test.d
gcc: directory/test.o: No such file or directory
Better way is to use python equivalent of execlp(3) or execvp(3).
--
Summary: dtrace: Incorrect shell execution
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: runtime
AssignedTo: systemtap at sources dot redhat dot com
ReportedBy: eugen at debian dot org
http://sourceware.org/bugzilla/show_bug.cgi?id=9850
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next reply other threads:[~2009-02-15 21:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-16 12:16 eugen at debian dot org [this message]
2009-02-16 14:21 ` [Bug runtime/9850] " mjw at redhat dot com
2009-02-16 14:37 ` eugen at debian dot org
2009-02-16 19:53 ` mjw at redhat dot com
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=20090215212534.9850.eugen@debian.org \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).