... so run it inside hwpmc and see what the resulting CPU users are?
adrian
On 31 May 2013 07:01, Chris Rees wrote:
> Hi all,
>
> I think I've discovered a strange behaviour of sed perhaps triggered
> by the length of a regex passed to it. I noticed that a certain
> expression I passed took a
On 2 June 2013 18:15, Florent Peterschmitt wrote:
> Le 02/06/2013 14:16, Chris Rees a écrit :
>> On 2 June 2013 11:41, Eduardo Morras wrote:
>>> On Fri, 31 May 2013 15:01:59 +0100
>>> Chris Rees wrote:
>>>
Hi all,
I think I've discovered a strange behaviour of sed perhaps triggere
Le 02/06/2013 14:16, Chris Rees a écrit :
> On 2 June 2013 11:41, Eduardo Morras wrote:
>> On Fri, 31 May 2013 15:01:59 +0100
>> Chris Rees wrote:
>>
>>> Hi all,
>>>
>>> I think I've discovered a strange behaviour of sed perhaps triggered
>>> by the length of a regex passed to it. I noticed that
On 2 June 2013 11:41, Eduardo Morras wrote:
> On Fri, 31 May 2013 15:01:59 +0100
> Chris Rees wrote:
>
>> Hi all,
>>
>> I think I've discovered a strange behaviour of sed perhaps triggered
>> by the length of a regex passed to it. I noticed that a certain
>> expression I passed took a very long
On Fri, 31 May 2013 15:01:59 +0100
Chris Rees wrote:
> Hi all,
>
> I think I've discovered a strange behaviour of sed perhaps triggered
> by the length of a regex passed to it. I noticed that a certain
> expression I passed took a very long time, and suspected the usual
> backtracking loop, so
Le 31/05/2013 16:01, Chris Rees a écrit :
> Hi all,
>
> I think I've discovered a strange behaviour of sed perhaps triggered
> by the length of a regex passed to it. I noticed that a certain
> expression I passed took a very long time, and suspected the usual
> backtracking loop, so I started tri
6 matches
Mail list logo