Re: crashed gawk '{one!=one=$1}'

[Dan Jacobson]

>>>>> "A" == Aharon Robbins <address@hidden> writes:

A> Greetings. Re this:
>> To: address@hidden
>> From: Dan Jacobson <address@hidden>
>> Subject: crashed gawk '{one!=one=$1}'
>> 
>> I am proud to say that I have crashed gawk:

A> Gee, why does this make you "proud"?  Got something personal
A> against me?

No, silly.  I'm proud to have helped you find hard to find bugs and
thus further help the free software effort... like winning a Knuth TeX
bug reward... just forgot the smiley, thats all :-)

That my contribution comes not from expert programming but mainly from
typos is well, better than nothing.

>> It was a typo, I didn't do it on purpose.  No I haven't tried to
>> figure out what '{one!=one=$1}' means.  All I know is that
>> "Segmentation fault" is just too cold a response.

A> This was a memory corruption problem that was an absolute bear to
A> track down.  Thanks for the simple program to reproduce it though.

OK, that's nice you found it.  Glad to help.  OK now lets get back to business.

P.S. what I really need is to find some bash bugs.  That ought to earn
me some respect around here, as Rodney Dangerfield said.  Every time I
think I find one it's always "no, that is explained by the standard,
line 34212. sorry, try harder" etc.  All I'm able to do on
gnu.bash.bug is to come up with some wimpy "suggestions" :-(

And then of course there are the tons of what I mistakenly thought
were bugs but were indeed features, as Eli has pointed out.

And then why don't I ever post in *.help and only *.bug: well its
because I'm reporting a deficiency in the help system as it lacked a
certain answer :-)

And why can't I be funny without adding that silly smiley symbol?
OK, I think I am quite boring at this point, OK, back to business.
--
http://www.geocities.com/jidanni Tel+886-4-25854780