[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
gawk crash with long floating-point numbers
|
From: |
Joseph S. Myers |
|
Subject: |
gawk crash with long floating-point numbers |
|
Date: |
Thu, 3 Nov 2005 22:59:03 +0000 (UTC) |
Running "gawk -f zex2 </dev/null" with the attached testcase script zex2
yields a crash with gawk 3.1.5 on i686-pc-linux-gnu:
9999999999999999860310597602564577717002641838126363875249660735883565852672743849064846414228960666786379280392654615393353172850252103336275952370615397010730691664689375178569039851073146339641623266071126720011020169553304018596457812688561947201171488461172921822139066929851282122002676667750021070848.000000
9999999999999999860310597602564577717002641838126363875249660735883565852672743849064846414228960666786379280392654615393353172850252103336275952370615397010730691664689375178569039851073146339641623266071126720011020169553304018596457812688561947201171488461172921822139066929851282122002676667750021070848.000000***
glibc detected *** double free or corruption (!prev): 0x080979a8 ***
Aborted (core dumped)
As glibc detecting corruption of malloc data, the exact symptoms may vary
from system to system; another gave "*** glibc detected *** free():
invalid next size (normal): 0x00000000006481a0 ***".
--
Joseph S. Myers
address@hidden
zex2
Description: Text document
- gawk crash with long floating-point numbers,
Joseph S. Myers <=