This is the mail archive of the mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

g++/binutils fragility

Sorry to be posting a problem without suggesting a solution.  I have a piece of C++ code which I have received from one of my
co-workers.  Making a few changes to make it acceptable to g++, without changing its behavior on the original compilers, I find that
it produces a SIGSEGV  under the stock cygwin installation (repeatedly so, over a number of setup.exe refreshes).  I grabbed the
binutils-20001029-2 source and built and installed it; the problem went away.  I set the alignment parameter in bfd/coff-i386.c to
(3) (64-bit alignments) and it re-appeared. The thing runs reliably in RH linux with gcc-2.95.2, but not with the commercial alpha
test compiler which I have.

I have been building binutils with CFLAGS='-Os -march=pentiumpro -pipe';  I've wondered whether there are any alignment problems
which would require more than one package to be built with identical compiler version and options and bfd alignment settings.

When I run under gdb, I am unsuccessful in attempting to step into the functions where the fault occurs; the cursor winds up on the
final "}" of one function or another.  This did not change with the latest experimental gdb.

I apologize for these struggles of an old Fortran programmer, but I have eliminated the warnings and complaints produced by the
various compilers, and still I have this effect: in summary,

 installing binutils from cygwin source produces reliable operation; installing the cygwin binary does not.


Want to unsubscribe from this list?
Send a message to

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]