The test case is all of the files in the attached gcc-3.4.4-bug-test-case.tar.gz. I sent the sample instead of the preprocessed files because the bug only presents itself when the base class code is in a library. If you include it in the main file or just link it in as a .o, the code works fine.
This is probably isn't an absolute minimal test case, but it's not far off.I have included cygcheck.out.gz as per Cygwin bug reporting instructions in case it's needed/wanted. I gzipped it to avoid the verbosity in the message for those who don't care.
I submitted this to the cygwin mailing list and was asked to report it as a gcc bug. I looked at entering it into the bugzilla database, but I didn't see a way to easily give you this type of test case using that mechanism.
Please let me know if I have misssed some needed information. John gcc version (results of gcc -v) Reading specs from /usr/lib/gcc/i686-pc-cygwin/3.4.4/specs Configured with: /gcc/gcc-3.4.4/gcc-3.4.4-1/configure --verbose --prefix=/usr --exec-prefix=/usr --sysconfdir=/etc --libdir=/usr/lib --libexecdir=/usr/lib --mandir=/usr/share/man --infodir=/usr/share/info --enable-languages=c,ada,c++,d,f77,java,objc --enable-nls --without-included-gettext --enable-version-specific-runtime-libs --without-x --enable-libgcj --disable-java-awt --with-system-zlib --enable-interpreter --disable-libgcj-debug --enable-threads=posix --enable-java-gc=boehm --disable-win32-registry --enable-sjlj-exceptions --enable-hash-synchronization --enable-libstdcxx-debug : (reconfigured) Thread model: posix gcc version 3.4.4 (cygming special) (gdc 0.12, using dmd 0.125) system (results of uname -a) CYGWIN_NT-5.0 trivia 1.5.17(0.129/4/2) 2005-05-25 19:38 i686 unknown unknown Cygwin command line (see Makefile and baselib.mak) There are no compiler warnings or errors.
cygcheck.out.gz
Description: application/gzip
gcc-3.4.4-bug-test-case.tar.gz
Description: application/gzip