A few more details on the crash with the qt-x11+gcc-2.95.3+cygwin build that I reported a few days ago.
I traced (with the help of my wife) the crash to the call to std:getline in support/filetools.C, and I was able to duplicate the crash with a very short program. This happens with gcc-2.95.3 but not with gcc-3.3.1 on cygwin. So I think that there is some bug in this function (std::getline) in this version of gcc. The function is coming from a template in bastring.cc.
I am using 2.95 since I was not able to compile Qt with 3.3.
Another workaround that I tried is to use --with-included-string in the configure setup, but that failed because boost insisted on trying to #include <limit>.
If anybody has an idea, either on how to fix or get around the getline bug, or how to build lyx with --witn-included-string (which I think will use another getline), please let me know.
This saga might have some impact on the recent thread on qt3 noncommercial.
Sivan
- Re: More specifics on the gcc-2.95.3 cygwin crash Sivan Toledo
- Re: More specifics on the gcc-2.95.3 cygwin crash Angus Leeming
- Re: More specifics on the gcc-2.95.3 cygwin crash Georg Baum
- Re: More specifics on the gcc-2.95.3 cygwin cr... Sivan Toledo
- Re: More specifics on the gcc-2.95.3 cygwin cr... Martin Vermeer