Bug 82392 - Specifying env variables on strace cmdline
Specifying env variables on strace cmdline
Status: CLOSED RAWHIDE
Product: Red Hat Linux Beta
Classification: Retired
Component: strace (Show other bugs)
beta5
All Linux
medium Severity medium
: ---
: ---
Assigned To: Roland McGrath
Brian Brock
: FutureFeature
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-01-21 15:27 EST by Jakub Jelinek
Modified: 2007-04-18 12:50 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-02-19 22:58:09 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Jakub Jelinek 2003-01-21 15:27:05 EST
I think it would be good idea if strace accepted NAME=VALUE
arguments before name of command it should run and put them
into environment, so that if I want to see what:
LD_TRACE_LOADED_OBJECTS=1 ./somebinary
actually does, I can run:
strace LD_TRACE_LOADED_OBJECTS=1 ./somebinary
Similarly LD_LIBRARY_PATH, when I want strace itself use different
one from what I want for the binary, etc.

Roland:
That is reasonable, though perhaps -E foo=bar instead of breaking
either funny-named files or funny-named envvars.  Of course you can
always strace env foo=bar blah and ignore the part before the execve.
Comment 1 Roland McGrath 2003-01-21 23:45:39 EST
I implemented it upstream, but after the 4.4.93 release.
The next release will have the -E switch.
Comment 2 Roland McGrath 2003-02-19 22:58:09 EST
4.4.94 release has the feature and will hit rawhide soon enough.

Note You need to log in before you can comment on or make changes to this bug.