From: Luke Dunstan <coder_infidel@ho...> - 2003-05-03 18:35:00
>From: "jinlong" <jinlong@...>
>Subject: [Mingw-users] Win2k linker library socket console class log
>Date: Sat, 3 May 2003 06:39:01 -0700
>I did a socket program. In the program I am using
>socket, send recv, connect, etc. for a client program
>which is a simple class program. It is a cpp console program.
>(It is not supposed a windows program)
>It can be compiled well without errors or (warnings?) by using
>c:\ gcc -o aaa aaa.cpp -lwsock32 -lstdc++
>when run, I got a popup showing:
>xxx has generated errors and will be closed by windows. you will need
>to restart the program.
>An error log is being created (OK)
>It starts the main and goes to a class method and down immediately
>(pop up the above message and die).
>1. is the compiling-linking command right? if so, what is the right one?
>2. does it get the right wsock32.dll or should I use
>libwsock32.a instead? if so, how can I call libwsock32.a
>I see libwosck32.a is under c:\minge\lib
>so do I have to use this one instead of the wsock32.dll under
>3. why is the reason it just could run on my environment?
>4. where is the log file (say in the popup screen) I can find
It would be easier to find the location of the crash using GDB or drmingw
(from the mingw-utils package). It does seem like a bug in your code though,
so if you need further help it would be best if you post the source code for
a small test case that shows the problem, then other people can try it
>o. thank you all very much for any response and help.
>Here is the gcc infomation:
>Reading specs from c:/MinGW/bin/../lib/gcc-lib/mingw32/3.2.2/specs
>Configured with: ../gcc/configure --with-gcc --with-gnu-ld --with-gnu-as
>mingw32 --target=mingw32 --prefix=/mingw --enable-threads --disable-nls
>-languages=c++,f77,objc --disable-win32-registry --disable-shared
>Thread model: win32
>gcc version 3.2.2 (mingw special 20030208-1)
MSN Instant Messenger now available on Australian mobile phones. Go to