This is the mail archive of the
cygwin@sourceware.cygnus.com
mailing list for the Cygwin project.
gdb emits error message, Exception: STATUS_ACCESS_VIOLATION
- To: <cygwin at sourceware dot cygnus dot com>
- Subject: gdb emits error message, Exception: STATUS_ACCESS_VIOLATION
- From: "Sung-taek Lim" <totohero at poppy dot snu dot ac dot kr>
- Date: Wed, 7 Jun 2000 18:55:56 +0900
Hello, I'm modifying gdb 4.18 to support parallel port remote debugging.
I've linked an object file which contains references to _inp, _outp functions to
gdb executable. And with additional option -luser32 and -lmsvcrt the make
procedure completed without any problem. But when I execute the gdb.exe
it emits following message,
[main] D:\CYGNUS\CYGWIN-B20\WORK\GDB_BUILD\BUILD\GDB\GDB.EXE 6196 (0) handle_exc
eptions: Exception: STATUS_ACCESS_VIOLATION
[main] GDB 6196 (0) handle_exceptions: Dumping stack trace to GDB.EXE.core
When I excluded the object file it didn't make any difference. I think the problem is
'-luser32' or '-lmsvcrt' option. Can anybody explain this please?
Thanks in advance.
Sung-taek.