Date:	Sun, 22 Nov 1998 14:47:36 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	Ron Miller <rmiller AT synopsys DOT com>
cc:	djgpp AT delorie DOT com
Subject:	Re: Help with GDB ... gdb always exits and stdout goes missing
In-Reply-To:	<3657670A.7BE5E06@synopsys.com>
Message-ID:	<Pine.SUN.3.91.981122144716.17686Z-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp AT delorie DOT com

On Sat, 21 Nov 1998, Ron Miller wrote:

> 1) If I set a breakpoint and then continue, the debugger exits when I
> continue. For example, here is the output of running a "hello world"
> program ...
[snip] 
> Note that when I stepped into the program and then continued, the
> debugger exited when the program being debugged finished.
> 
> 2) Also ... when stepping through a program, stdout doesn't seem to be
> displayed. If you notice in the above output, "hello world" was
> displayed when I ran the program with no breakpoints, but was nowhere to
> be seen when I stopped in main and then continued.

I have never seen these problems.  Please post more details about the
program and your setup:

	1) The type and version of your operating system (DOS?
           Windows? what version?).

	2) The size and time stamp of gdb.exe you are using, and what
           was the name of the zip file you got it from.

	3) The source of the program you were debugging, the GCC
           command used to compile and link it, and the GDB command
           line used to invoke the debugger.

	4) The version of GCC you used to compile and link your
           program.

FYI, the deviation of the GDB operation on DOS/Windows from what it
does on Unix are spelled out in section 12.1 of the DJGPP FAQ list.
None of what you report comes close to what's described there.

- Raw text -