public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Roberto Nibali <ratz@drugphish.ch>
To: vda@port.imtp.ilyichevsk.odessa.ua
Cc: linux-kernel@vger.kernel.org
Subject: Re: Improved ksymoops output
Date: Thu, 14 Feb 2002 02:30:16 +0100	[thread overview]
Message-ID: <3C6B1328.3060506@drugphish.ch> (raw)
In-Reply-To: <200202130805.g1D85st16817@Port.imtp.ilyichevsk.odessa.ua> <3C6A3C26.4050908@drugphish.ch> <200202131223.g1DCN5t17824@Port.imtp.ilyichevsk.odessa.ua>

Hi,

[reduced cc list, since I don't think the rest of the guys are 
interested in non-kernel related things]

> As already pointed out, format is horrendous, but prettier format
> requires much more serious hacking in ksymoops sources instead of my
> quick and very dirty tricks.

Yep, I see. After rethinking about this I have to agree with Russell. 
And I mean you still can't educate people to read FAQ's and manuals. 
Even with your output people that have no knowledge about this output 
will the things you mentioned as rationale. If one sees your inital oops 
where the hell does he get the information about calling your scripts 
without reading some document you must be providing. Well, and if he 
needs to read your docu he can as well read oops-tracing.txt. This is my 
little world, YMMV.

>>o run faster (5%) ;)
>>o should never have problems when one day there will be a lot of *.c
>>   files. In your approach LIST could someday not hold all entries
>>   anymore.
>>
> 
>>o simplifies the bash 'regexp' to snip away the '.c' and print the rest
>>
> 
> Hmm... is it faster than original?

I would say so, "b=${a%.*}" is always faster and legible than
                 "l=$((${#a}-2)); b=${a:0:$l}"
in the way it is used in your script.

Maybe not easily measurable but it seems obvious to me and is easier to 
read and overall time reported less time used for the whole script to 
run. ;)

And the second tiny cleanup regarding regexp was to use "${a:2}" instead 
of "${a:2:9999}". It should be an improvement too, if I remember the 
bash source correctly. But this is senseless nitpicking. The real speed 
improvement you get by avoiding the "LIST=`find -name '*.c' | xargs`".

>>I'm propably going to rewrite the python script in bash too, since I
>>don't run python on my distro (and I do not intend to use 2.5.x anytime
>>soon).
>>
> 
> Care to show the result to me?

Well, if there is a real interest from other parties, I will definitely 
spend some time to do it. OTOH, bash's regexp handling isn't as strong 
as python's AFAICS so it might be a pain in the ass to do it but this is 
getting off-topic.

Best regards,
Roberto Nibali, ratz


  parent reply	other threads:[~2002-02-14  1:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-13 12:05 Improved ksymoops output Denis Vlasenko
2002-02-13 10:12 ` Roberto Nibali
     [not found]   ` <200202131223.g1DCN5t17824@Port.imtp.ilyichevsk.odessa.ua>
2002-02-14  1:30     ` Roberto Nibali [this message]
2002-02-13 10:15 ` Russell King
2002-02-14 16:02   ` Denis Vlasenko

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3C6B1328.3060506@drugphish.ch \
    --to=ratz@drugphish.ch \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vda@port.imtp.ilyichevsk.odessa.ua \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox