2014-03-21 11:08 GMT-04:00 Dmitry V. Levin :
> On Fri, Mar 21, 2014 at 10:49:55AM -0400, Marc-Antoine Ruel wrote:
> [...]
>> Yes I'm on 4.5.20. I mildly recall hitting problems when trying to
>> compile strace's tip of tree since I think (?) it required a newer gcc
>> version than the stock one (4.
On Fri, Mar 21, 2014 at 10:49:55AM -0400, Marc-Antoine Ruel wrote:
[...]
> Yes I'm on 4.5.20. I mildly recall hitting problems when trying to
> compile strace's tip of tree since I think (?) it required a newer gcc
> version than the stock one (4.6.3) in 12.04. That was in 2012. At that
> point, I
We got a race conditions with our emails, sorry for the duplicated arguments.
In short, we are in agreement.
2014-03-21 9:43 GMT-04:00 Philippe Ombredanne :
> In your case using the standard Python shlex module may be of some help?
Eh, definitely a lack of knowledge on my part as I didn't know
On Fri, Mar 21, 2014 at 2:35 PM, Philippe Ombredanne
wrote:
> On Thu, Mar 20, 2014 at 9:50 PM, Marc-Antoine Ruel
> wrote:
[...]
>> - Encoding, I had to write a state machine to read the logs properly, see
>> the >110 lines of strace_process_quoted_arguments(). That's independent of
>> -x.
>
> Ag
On Thu, Mar 20, 2014 at 9:50 PM, Marc-Antoine Ruel wrote:
> Hi,
Hi Marc-Antoine!
and thank you for this detailed feedback!
> I was pointed out to this thread. I wrote trace_inputs.py.
For reference I think the code you are talking about can be found at [1]
> It was used to
> isolate chromium t
Hi,
I was pointed out to this thread. I wrote trace_inputs.py. It was used to
isolate chromium tests and figure out which files are touched by each test
case. It doesn't care about anything except files being opened so strace
log parsing was kept to a minimum. Note that I've been mostly using the
