Bug 61317 - gawk is too fuzyy with --non-decimal-data
Summary: gawk is too fuzyy with --non-decimal-data
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: gawk
Version: 7.3
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Florian La Roche
QA Contact: Brock Organ
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-03-17 17:46 UTC by Ulrich Drepper
Modified: 2007-04-18 16:40 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2002-03-17 17:46:59 UTC
Embargoed:

Attachments (Terms of Use)
Patch to treat 0x as text (360 bytes, patch)
2002-03-17 17:46 UTC, Ulrich Drepper 		no flags Details | Diff
View All

Description Ulrich Drepper 2002-03-17 17:46:10 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9+) Gecko/20020315

Description of problem:
If the --non-decimal-data option is used and gawk sees "0x" in the input it
flags an error.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1.echo "0x" | gawk-3.1.0 --non-decimal-data '{print 0+$1}'
2.
3.
	

Actual Results:  gawk-3.1.0: builtin.c:2281: nondec2awknum: Assertion `len > 2'
failed.
Aborted


Expected Results:  "0x" should be treated like text.

Additional info:

I'll attach a patch soon which is similar to what will be in the next official
version of gawk.
Comment 1 Ulrich Drepper 2002-03-17 17:46:55 UTC 
Created attachment 48805 [details]
Patch to treat 0x as text
Comment 2 Florian La Roche 2002-03-17 18:02:12 UTC 
Patch added to 3.0.4-4.

Thanks,

Florian La Roche
Note You need to log in before you can comment on or make changes to this bug.