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: <004a01bfd11e$4becd6e0$8f742e93@snu.ac.kr>
From: "Sung-taek Lim" <totohero AT poppy DOT snu DOT ac DOT kr>
To: <cgf AT cygnus DOT com>, <cygwin AT sourceware DOT cygnus DOT com>
Subject: Re: gdb emits error message, Exception: STATUS_ACCESS_VIOLATION
Date: Thu, 8 Jun 2000 16:51:03 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ks_c_5601-1987"
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
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by delorie.com id DAA06077

>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

Thank you for your response. Of course I tried working gdb first but it 
gave no useful info. like this.

[totohero AT claudia build]$ gdb gdb/gdb.exe
GNU gdb 4.17.1
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i586-cygwin32"...
(gdb) run
Starting program: file://D/cygnus/cygwin-b20/work/gdb_build/build/gdb/gdb.exe
78000000:/WINDOWS/SYSTEM/MSVCRT.DLL
bff20000:/WINDOWS/SYSTEM/GDI32.DLL
bff50000:/WINDOWS/SYSTEM/USER32.DLL
bff70000:/WINDOWS/SYSTEM/KERNEL32.DLL
bfea0000:/WINDOWS/SYSTEM/ADVAPI32.DLL
61000000:/bin/CYGWIN1.DLL

Program received signal SIGSEGV, Segmentation fault.
0xbff7b997 in _size_of_stack_reserve__ ()
(gdb) up
Cannot access memory at address 0x2000000.
(gdb)

I can't figure out what to do next.