Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sourceware.cygnus.com Delivered-To: mailing list cygwin@sourceware.cygnus.com From: Chris Faylor Date: Wed, 7 Jun 2000 14:08:23 -0400 To: cygwin@sourceware.cygnus.com Subject: Re: gdb emits error message, Exception: STATUS_ACCESS_VIOLATION Message-ID: <20000607140823.A15311@cygnus.com> Reply-To: cygwin@sourceware.cygnus.com Mail-Followup-To: cygwin@sourceware.cygnus.com References: <001001bfd066$93625580$8f742e93@snu.ac.kr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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@sourceware.cygnus.com