[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: fstream.write() sigsegv's on cygwin
From: |
jeffsp |
Subject: |
Re: fstream.write() sigsegv's on cygwin |
Date: |
22 Feb 2005 18:42:03 -0800 |
User-agent: |
G2/0.2 |
My original post contains a backtrace. Here it is again:
(gdb) run
Starting program: .../a.exe
Program received signal SIGSEGV, Segmentation fault.
0x610ec603 in cygwin1!_alloca () from /usr/bin/cygwin1.dll
(gdb) bt
#0 0x610ec603 in cygwin1!_alloca () from /usr/bin/cygwin1.dll
#1 0x61029f65 in cygwin_internal () from /usr/bin/cygwin1.dll
#2 0x6109ad7c in getppid () from /usr/bin/cygwin1.dll
#3 0x6108e1ef in cygwin1!aclcheck () from /usr/bin/cygwin1.dll
#4 0x0042e787 in std::basic_filebuf<char, std::char_traits<char>
Here is a summary of results on various platforms:
FAIL: win2K/cygwin/gcc 3.4.3
OK: win2k/cygwin/gcc 3.3.3
OK: win2k/msvc 7.1 OK
OK: linux/gcc 3.3.3
OK: linux/gcc 3.4.3
Is there anyone out there running the latest version of cygwin and gcc
that could try it on their machine?