| | [ Return to Bugs & Features | Roadmap 1.1 | SVN ⇄ GIT ]
STR #268
| Application: | FLTK Library |
|---|
| Status: | 1 - Closed w/Resolution |
|---|
| Priority: | 5 - Critical, e.g. nothing working at all |
|---|
| Scope: | 3 - Applies to all machines and operating systems |
|---|
| Subsystem: | Core Library |
|---|
| Summary: | Fl_Value_Input SegFaults using specified step() with huge values. |
|---|
| Version: | 1.1.4 |
|---|
| Created By: | sean.mcinerney |
|---|
| Assigned To: | mike |
|---|
| Fix Version: | 1.1.5rc1 |
|---|
| Update Notification: | |
|---|
Trouble Report Files:
| |
| #1 | sean.mcinerney
09:42 Feb 01, 2004 |
| test.cxx
1k | |
Trouble Report Comments:
| |
| #1 | sean.mcinerney
09:42 Feb 01, 2004 |
| Calling Fl_Value_Input::value(double) with a huge number (1.0e+299) after setting the step size to 0.001 results in a segmentation violation. Interestingly, this does not occur with the value 1.0e+99 and may, therefore, indicate a buffer size assumption.
Formatting with a step size of 0.001 with huge numbers is obviously silly, but can occur when such values flag a default state while normally entered values make sense. The ability to fall back on an alternate formatting (%e or %g) would be better than a core dump in these circumstances.
The included file 'test.cxx' illustrates the problem. | |
| |
| #2 | mike
17:42 Feb 25, 2004 |
| Fixed in CVS - the anonymous CVS repository will be updated at midnight PST. | |
[ Return to Bugs & Features ]
|
| |
