delorie.com/archives/browse.cgi | search |
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 |
From: | Chris Faylor <cgf AT cygnus DOT com> |
Date: | Wed, 7 Jun 2000 14:08:23 -0400 |
To: | cygwin AT sourceware DOT cygnus DOT com |
Subject: | Re: gdb emits error message, Exception: STATUS_ACCESS_VIOLATION |
Message-ID: | <20000607140823.A15311@cygnus.com> |
Reply-To: | cygwin AT sourceware DOT cygnus DOT com |
Mail-Followup-To: | cygwin AT sourceware DOT cygnus DOT com |
References: | <001001bfd066$93625580$8f742e93 AT snu DOT ac DOT kr> |
Mime-Version: | 1.0 |
User-Agent: | Mutt/1.2i |
In-Reply-To: | <001001bfd066$93625580$8f742e93@snu.ac.kr>; from totohero@poppy.snu.ac.kr on Wed, Jun 07, 2000 at 06:55:56PM +0900 |
On Wed, Jun 07, 2000 at 06:55:56PM +0900, Sung-taek Lim wrote: >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? If you're going to be modifying gdb, you'd better familiarize yourself with problems like this. You have a problem in gdb. The way to debug it is to debug gdb using a working copy of gdb, just like you would for UNIX. cgf -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |