Bug 56536
Summary: | Floating point exception bombs | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Michal Jaegermann <michal> |
Component: | xsane | Assignee: | Tim Waugh <twaugh> |
Status: | CLOSED RAWHIDE | QA Contact: | David Lawrence <dkl> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.2 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2002-01-08 16:05:56 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Michal Jaegermann
2001-11-20 18:26:27 UTC
Sigh! Yesterday it was bombing out always and today I cannot reproduce that anymore; neither with a debugging version nor with original executables. But the difference is that today I have recompiled sane-backends due to a bug #56540. The 0.81 changelog mentions floating point exceptions. I wonder if that fixes it. Is it previews that this happens with? Both! That means that if jpeg format was chosen then attempts to get anything out of a scanner caused an immediate floating point exception and exit from xsane. But by the time I atttempted to debug that it mysteriously vanished. On the top of that I do not an access to that scanner anymore as it went to its real owner. I'm going to mark this as closed, since I can't reproduce it here and both xsane and sane have had floating point problems fixed recently. |