Bogus FPE on underflow for exp(double)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
eglibc (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Precise |
Fix Released
|
Medium
|
Adam Conrad |
Bug Description
SRU Justification:
[Impact]
exp() in eglibc causes occasional FP crashes.
[Development Fix]
This is fixed in quantal.
[Stable Fix]
The fix can be backported to quantal.
[Test Case]
Test case is documented in the upstream bug:
http://
[Regression Potential]
Changes __kernel_standard_f to __kernel_standard in __exp in eglibc.
--
Glibc version 2.15 has a bug causing spurious FP crashes when calling exp(). It has been reported here:
http://
You can find all the details, including a testcase and the patch for libm in this report. I found that the 64-bit version of precise ships a version of glibc that still has this bug. I have not tested the 32-bit version, but I assume it has the same problem.
I am one of the developers of the open source code Cloudy and this bug renders our code completely non-functional. I would therefore like to urge you to ship this patch as an update for the precise distribution, especially since this is a LTS release.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: libc6 2.15-0ubuntu10
ProcVersionSign
Uname: Linux 3.2.0-24-generic x86_64
NonfreeKernelMo
ApportVersion: 2.0.1-0ubuntu8
Architecture: amd64
Date: Fri Jun 1 16:33:54 2012
InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
ProcEnviron:
LC_TIME=en_DK.utf8
TERM=vt100
LANG=en_US.UTF-8
SHELL=/bin/tcsh
SourcePackage: eglibc
UpgradeStatus: Upgraded to precise on 2012-05-07 (25 days ago)
Changed in eglibc (Ubuntu Precise): | |
status: | New → Confirmed |
Changed in eglibc (Ubuntu Precise): | |
assignee: | nobody → Adam Conrad (adconrad) |
importance: | Undecided → Medium |
description: | updated |
tags: |
added: verification-done removed: verification-needed |
Changed in eglibc (Ubuntu Precise): | |
status: | Fix Committed → Fix Released |
Is anybody looking at this? This is a critical bug that completely breaks our code. Many of our users have Ubuntu installed and are suffering because of this. So a quick fix would be appreciated. The link shown above contains the patch, so fixing this should be easy and quick. An identical bug report against openSUSE was fixed in 28 hours. This report is already more than 3 weeks old...