On 21 May 2012 17:52, Ted Kremenek <[email protected]> wrote: > On May 21, 2012, at 5:46 PM, Nick Lewycky <[email protected]> wrote: > > Good point. That can be fixed by changing to "my $command = $commandStr > 2>&1" can't it? Something like this: > > open(IN, "$commandStr 2>&1 |") or die $BAD; > > or were you trying to keep stdout and stderr output separate? Your current > command doesn't. > > > Now I remember. I wanted the output file for post-debugging if necessary. > I'd prefer to keep it as is. >
Okay!
_______________________________________________ cfe-commits mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits
