delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2000/06/07/10:58:26

Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
Message-ID: <001001bfd066$93625580$8f742e93@snu.ac.kr>
From: "Sung-taek Lim" <totohero AT poppy DOT snu DOT ac DOT kr>
To: <cygwin AT sourceware DOT cygnus DOT com>
Subject: gdb emits error message, Exception: STATUS_ACCESS_VIOLATION
Date: Wed, 7 Jun 2000 18:55:56 +0900
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
X-MIME-Autoconverted: from base64 to 8bit by delorie.com id KAA19442

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.

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019