Bug 82392

Summary: Specifying env variables on strace cmdline
Product: [Retired] Red Hat Linux Beta Reporter: Jakub Jelinek <jakub>
Component: straceAssignee: Roland McGrath <roland>
Status: CLOSED RAWHIDE QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: beta5Keywords: FutureFeature
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2003-02-20 03:58:09 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jakub Jelinek 2003-01-21 20:27:05 UTC 
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-22 04:45:39 UTC 
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-20 03:58:09 UTC 
4.4.94 release has the feature and will hit rawhide soon enough.