Re: Strange atof and strtof behaviors
Today, I ran on the Fedora installation the binary produced with the Debian installation. Guess what? Yes, it worked like a charm!
Now the strange thing. I ran on the Debian installation the binary produced with the Fedora installation. Segfaults due to the atof returning 0 rather than 0.189.
So, the problem isn't at compile time, but at runtime, and only on the Debian installation. I'm still wondering what's going wrong, since a simple C++ program with a single call to atof runs flawlessly on my Debian installation.
2008/8/9 Émeric Maschino <email@example.com>
Today, I recompiled the whole project on my Fedora installation using the updated gcc 4.3.1-4 packages from Rawhide. No problem with gcc 4.3.1 on my Fedora installation.
By contrast, despite a complete recompile with gcc 4.3.1 on my Debian Lenny installation, atof and strtof still behave incorrectly!
Is there any significant patch applied by Debian on the gcc 4.3.1 upstream code (or any related package) that could explain this situation?
2008/8/8 Émeric Maschino <firstname.lastname@example.org>
I have free time to play Fedora 9 "Sulphur" on my hp workstation zx6000.
The exact same C++ project (since the source code is on a separate partition) runs as expected on Fedora.
gcc version is 4.3.0 20080428.
My Debian Lenny installation comes with gcc 4.3.1.
Has something changed between gcc 4.3.0 and 4.3.1 regarding the standard C/C++ header inclusion?
I'm really running out of ideas...