X-Authentication-Warning:	ieva01.lanet.lv: pavenis owned process doing -bs
Date:	Thu, 20 May 1999 13:36:21 +0300 (WET)
From:	Andris Pavenis <pavenis AT lanet DOT lv>
To:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
cc:	djgpp-workers AT delorie DOT com
Subject:	Re: gdb 4.18 for DJGPP (alpha)
In-Reply-To:	<Pine.SUN.3.91.990520094344.22291D-100000@is>
Message-ID:	<Pine.A41.4.05.9905201327380.92326-100000@ieva01.lanet.lv>
MIME-Version:	1.0
Reply-To:	djgpp-workers AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Thu, 20 May 1999, Eli Zaretskii wrote:

> I'm trying to remove unnecessary #ifdef __GO32__ in GDB sources, and I 
> have bumped into some strange snag.  I'm still investigating this, so the 
> info below is admittedly incomplete; I simply want to know if this is a 
> known problem and if somebody could give me a hint where to look.
> 
> Here's the deal: I enabled signal handling in readline (see 
> readline/signals.c in the GDB sources) by removing "#undef HANDLE_SIGNALS"
> at the beginning of the file.  Source inspection seems to indicate that 
> the code in signals.c doesn't do anything bad or unsupported by DJGPP.  
> However, the resulting gdb.exe seems to work well when debugging other 
> programs, including if I press Ctrl-C, but crashes when debugging itself.
> 
> Specifically, the following sequence of commands leads to a crash:
> 
> 	gdb gdb.exe
> 	run
> 	help info
> 	Ctrl-C
> 
> (I press Ctrl-C after the inferior GDB displays the first screenful of 
> the help info and prompts me to press Enter or q.)
> 
> The inferior GDB is killed when I press Ctrl-C (which I understand is the 
> correct behavior), but then the parent GDB gets SIGSEGV and dies.
> 
> The traceback is also strange: the App stack it displays has its limits 
> reversed, i.e., in the [addr1..addr2] display addr1 is less than addr2!
> (I will post the full traceback later.)
> 
> Does this ring a bell for someone?  Is it at all reasonable to expect GDB 
> be debugged by itself in a stable manner?  Does v2.02 include known bugs 
> in libdbg.a that could produce such problems?

Build gdb-4.18 with upcoming DJGPP-2.03. Ctrl-C will kill debugee if gdb
is built with earlier versions (before You checked in updated dbgcom.c).
At least I have successfully debugged debugger part in rhide with itself
(with gdb-4.17 not 4.18, but I don't think it's a problem as such
possibility is determined by dbgcom.c)

Also You should apply patch to gdb/go32-nat.c sent recently to this
mailing list. I sent it together with some other patches, but Robert
resent this only to be checked in.

> 
> Any help will be most appreciated.
> 

Andris

- Raw text -