Closed Bug 664523 Opened 14 years ago Closed 14 years ago

Invalid number to string conversion (corruption ?)

Categories

(Rhino Graveyard :: Core, defect)

Product:
Rhino Graveyard
Component:
Core
Platform:
x86_64
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: drazzib, Unassigned)

References

(
URL
)

Details

User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.71 Safari/534.24 Build Identifier: 1.7R3 It seems there is some memory corruption in to string conversion from big numbers: js> m = 2.2250738585072014e-308 2.2250738585072014e-308 js> m * 0.99 F.028231199221293e-309 Reproducible: Always Steps to Reproduce: js> m = 2.2250738585072014e-308 2.2250738585072014e-308 js> m * 0.99 F.028231199221293e-309 js> m * 0.999 F.228487846486944e-309 js> m * 0.98 E.805723813370573e-309 js> m * 0.95 E.13820165581841e-309 js> m * 0.91 D.248172112415536e-309 js> m * 0.8 A.80059086805761e-309 js> m * 0.5 ;.125369292536007e-309 js> m * 0.4 8.900295434028804e-309 js> m * 0.6 =.35044315104321e-309 js> m * 0.7 ?.57551700955041e-309 js> Actual Results: Chars appears in output. Expected Results: Rhino should only display numbers (converted and with reduced precision)
This is fixed by the fix for bug #548857 and also by porting V8-DToA.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.