[Bug 218161] New: gawk crashes
https://bugzilla.novell.com/show_bug.cgi?id=218161
Summary: gawk crashes
Product: SUSE Linux 10.1
Version: Final
Platform: i686
OS/Version: SuSE Linux 10.1
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Basesystem
AssignedTo: bnc-team-screening@forge.provo.novell.com
ReportedBy: ptaylor@quadlogic.fr
QAContact: qa@suse.de
Suse 10.1
$> uname -a
Linux web99 2.6.16.21-0.25-smp #1 SMP Tue Sep 19 07:26:15 UTC 2006 i686 i686
i386 GNU/Linux
$> rpm -qa | grep awk
gawk-3.1.5-18
$> gawk --version | head -n 1
GNU Awk 3.1.5
I came across a problem using a program 'cdb' which uses gawk, it crashes when
used.
After searching,I found another Suse 10.1 user Pablo Costa who had the same
problem. He created the following script to generate the error.
## Start
cd /tmp
# the script; PLEASE take care if you copy on your own file
# to remove the BACKSLASH just before the DOLLAR; It's
# there to prevent the shell from evaluating $i when copy/pasting.
cat > problem.awk <<-EOF
{
print "RECORD " NR;
for ( i = 0; length( \$i ) > 0; i++ ) print " FIELD " i " of " NF;
}
EOF
# It doesn't seem to really matter what kind of input you
# give to the script. Also it doesn't matter if it's given
# on a file via gawk command line invocation or if it's fed
# via stdin through a pipe.
cat > awk_example <
https://bugzilla.novell.com/show_bug.cgi?id=218161 cthiel@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team- |schwab@novell.com |screening@forge.provo.novell| |.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=218161 schwab@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED ------- Comment #1 from schwab@novell.com 2006-11-07 05:54 MST ------- This is already fixed. Use LC_ALL=C for a workaround. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=218161
User bugproxy@us.ibm.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=218161#c2
LTC BugProxy
https://bugzilla.novell.com/show_bug.cgi?id=218161
User bugproxy@us.ibm.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=218161#c3
LTC BugProxy
https://bugzilla.novell.com/show_bug.cgi?id=218161
User bugproxy@us.ibm.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=218161#c4
--- Comment #4 from LTC BugProxy
https://bugzilla.novell.com/show_bug.cgi?id=218161
User bugproxy@us.ibm.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=218161#c5
--- Comment #5 from LTC BugProxy
https://bugzilla.novell.com/show_bug.cgi?id=218161
User bugproxy@us.ibm.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=218161#c6
--- Comment #6 from LTC BugProxy
https://bugzilla.novell.com/show_bug.cgi?id=218161
User bugproxy@us.ibm.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=218161#c7
--- Comment #7 from LTC BugProxy
https://bugzilla.novell.com/show_bug.cgi?id=218161
User bugproxy@us.ibm.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=218161#c8
--- Comment #8 from LTC BugProxy
https://bugzilla.novell.com/show_bug.cgi?id=218161
User bugproxy@us.ibm.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=218161#c9
--- Comment #9 from LTC BugProxy
https://bugzilla.novell.com/show_bug.cgi?id=218161
User bugproxy@us.ibm.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=218161#c10
--- Comment #10 from LTC BugProxy
participants (1)
-
bugzilla_noreply@novell.com