[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: the profiling patch



On Fri, Mar 1, 2013 at 10:02 AM, Raphael Proust <raphlalou@xxxxxxxxx> wrote:
> On Fri, Mar 1, 2013 at 7:01 AM, Mark Shinwell <mshinwell@xxxxxxxxxxxxxx> 
> wrote:
>> On 28 February 2013 18:05, Anil Madhavapeddy <anil@xxxxxxxxxx> wrote:
>>> However, when I run it on a toy program, I get the expect
>>>
>>> $ ./a.out
>>> minor,0x404368,303
>>> minor,0x405bd0,5
>>> minor,0x405e48,2
>>> minor,0x4063c0,9
>>> minor,0x40ba48,12
>>> major,0x4151a8,72
>>> $ ./a.out > x
>>> $ ./parse.sh ./a.out x
>>> /tmp/tmp.fJkFjf9obV:1: Error in sourced command file:
>>> No symbol "minor" in current context.
>>> 303
>>> 72
>>> 12
>>> 9
>>> 5
>>> 2
>>>
>>> Where does this 'minor' symbol crop up from?
>>
>> You need to split the output into two files and delete the first
>> column from each ("minor," or "major,").  Did you miss that step?
>
> Can you add the following to your processing pipeline
>
> â | grep "^minor" | cut -b 7- | â
> â | grep "^major" | cut -b 7- | â

In fact, depending on support by your shell, you might do something like:
in zsh: ./parse.sh ./a.out <( cat x | grep "^minor" | cut -b 7- )
in rc: ./parse.sh ./a.out <{ cat x | grep "^minor" | cut -b 7- }

>
>
> --
> ______________
> RaphaÃl Proust



-- 
______________
RaphaÃl Proust



 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.