From:	swarnerx3 AT acadia DOT net (Scott Warner)
Subject:	Re: Debugging help needed
10 Nov 1997 22:34:51 -0800 :
Message-ID:	<199711102337.SAA11314.cygnus.gnu-win32@p2.acadia.net>
Mime-Version:	1.0
To:	"Fernandes, Hilton" <hfernandes AT geocities DOT com>
Cc:	<gnu-win32 AT cygnus DOT com>

Thank you for your help.  I compiled & linked with -g, but get a message
from gdb saying 'no debugging symbols found' or to that effect.  However,
this is probably something simple I can take care of with a little
homework.

> Third :-) There is a debugger in cygwin32, a. k. a. gnu-win32.  It is
called
> gdb and is the standard GNU debugger.  In cygwin it has a GUI face, but
the
> same commands.  It is very useful -- particularly in cases like yours --,
but
> it still demands some finishing touches.  Get acquainted with it through
the 
> "help" command, typed at the user prompt.
> 
> First and second :-) Usually the cygwin products work, even when need
> finishing touches.   So, the first thing to check is your use of
<iostream.h>
> classes.  My personal experience with it was not very good.  I hope yours
is
> better. :-)
> 
> Run your program through gdb and it will show the line where it broke. 
Then a 
> command named "where" will display the stack of functions when the
program 
> broke.
> 
> Don't forget to compile and link with the -g flag enabled.
> 
> 

-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".

- Raw text -