Before talking about reporting bugs, let’s define what is a bug, and what is not.
A bug is:
gawkbehaves differently from what’s described in the POSIX standard, and that difference is not mentioned in this Web page as being done on purpose.
gawkbehaves differently from what’s described in this Web page.
gawkbehaves differently from other
awkimplementations in particular circumstances, and that behavior cannot be attributed to an additional feature in
The following things are not bugs, and should not be reported
to the bug mailing list. You can ask about them on the “help” mailing
list (see Where To Send Non-bug Questions), but don’t be surprised if you get an
answer of the form “that’s how
gawk behaves and it isn’t
going to change.” Here’s the list:
The number of features that
gawk does not have is
by definition infinite. It cannot be all things to all people.
In short, just because
gawk doesn’t do what you
think it should, it’s not necessarily a bug.
awk. Even if you happen to dislike those behaviors, they’re not going to change: changing them would break millions of existing
gawkstand on their own and do not have to follow the crowd. This is particularly true when the requested behavior change would break backwards compatibility.
This applies also to differences in behavior between
and other language compilers and interpreters, such as wishes for more
detailed descriptions of what the problem is when a syntax error is
awkprogramming or why
gawkbehaves the way it does. For that use the “help” mailing list: see Where To Send Non-bug Questions.
For more information, see Fork My Code, Please!—An Open Letter To Those of You Who Are Unhappy, by Arnold Robbins and Chet Ramey.
A Note About Fuzzers
In recent years, people have been running “fuzzers” to generate
In general, such reports are not of much practical use. The programs they create are not realistic and the bugs found are generally from some kind of memory corruption that is fatal anyway.
So, if you want to run a fuzzer against