Strange crash for application linked to cygwin libraries.
Fri Oct 17 07:29:00 GMT 2008
Peter Ross writes:
> >> >> I've written an application which does some initialization and then
> >> >> does a tcp accept. 5 minutes and 20 seconds give or take after doing
> >> >> the tcp.accept the application aborts with exit code 0. If I
> >> >> continually send tcp data to this application then the crash doesn't
> >> >> occur, it is only after 5 minutes and 20 seconds of waiting for I/O.
> >> > [...]
> >> >> Here is the complete list of libraries that I use -lodbc32 -lole32
> >> >> -lraptor -lxslt -lcurl -lz -lxml2 -ldb -lssl -lcrypto -lexpat
> >> >> -lwsock32
> Find attached.
Thank you. I don't see anything obvious in the cygcheck -svr output that's out
of the ordinary. Rats.
> > Are all of those libraries you're linking with compiled for Cygwin? Mixing
> > Cygwin libs with non-Cygwin libs won't work.
> Yes they are all cygwin libraries.
> $ cygcheck.exe ./wos_server.exe
> So I am using the ODBC and OLE32 for access to CreateGUID, I don't
> think these are a problem, but I could be wrong.
I can't reconcile your comment earlier that all the libraries you're linking
against were compiled for Cygwin with the output of cygcheck ./wos_server.exe.
There are clearly system libraries being mentioned in the linker options,
libraries that weren't compiled for Cygwin.
I'm at the very limit of my meager knowledge on this subject, but I know it's
bad practice to have both cygwin1.dll and msvcrt.dll associated at the same
time. They have contradictory implementations of the same kinds of things.
Not being able to run strace on the app successfully is also very suspicious.
I suspect there's something simple about how you've linked your app that I'm
just not seeing here and I welcome any knowledgeable lurkers to chime in with
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
More information about the Cygwin