Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
To: cygwin AT sourceware DOT cygnus DOT com
Date: Sun, 21 Feb 1999 23:31:50 -0600
Subject: gdb failure
Message-ID: <19990221.233151.-251785.0.murli@juno.com>
MIME-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
From: Murli Ganeshan <murli AT juno DOT com>

Here's a transcript of a gdb session while trying to debug an ACCESS
VIOLATION bug.

(gdb) br test1
Breakpoint 1 at 0x402654
(gdb) r
Starting program: /c/MSDEV/Projects/hmwk3/exam.exe 
bff30000:/c/WINDOWS/SYSTEM/GDI32.DLL
bff60000:/c/WINDOWS/SYSTEM/USER32.DLL
bff70000:/c/WINDOWS/SYSTEM/KERNEL32.DLL
bfed0000:/c/WINDOWS/SYSTEM/ADVAPI32.DLL
61000000:/c/CYGNUS/CYGWIN-B20/H-I586-CYGWIN32/BIN/CYGWIN1.DLL

Breakpoint 1, 0x402654 in test1 ()
(gdb) s
Single stepping until exit from function test1__Fv, 
which has no line number information.

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

I was puzzled as to why the step (s) did not step thru the code line by
line. Can someone shed some light as to what could be the problem, like
how to trace the line in the source code that's trying to access memory
at 0x20000000?

thanks
murli
___________________________________________________________________
You don't need to buy Internet access to use free Internet e-mail.
Get completely free e-mail from Juno at http://www.juno.com/getjuno.html
or call Juno at (800) 654-JUNO [654-5866]

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com