Date: Thu, 18 Jan 2001 10:45:46 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Cesar Rabak <csrabak AT uol DOT com DOT br>
cc: djgpp AT delorie DOT com
Subject: Re: gdb 5.0 and yamd
In-Reply-To: <3A665B0E.6159A236@uol.com.br>
Message-ID: <Pine.SUN.3.91.1010118104522.3768O-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Thu, 18 Jan 2001, Cesar Rabak wrote:

> If we make the modifications, in order to submit the code and binaries
> modified, is there any kind of regression tests?

If you tried the testing script I put into the source distribution,
you could run it before and after the change.  It doesn't run the
entire test suite yet, but it's better than nothing.

But most important, simply use the debugger for some time in serious
work, and if it doesn't show any signs of problems, the changes are
probably right.  I have write access to the GDB CVS tree, so I can
commit changes specific to DJGPP if I think they are okay.

But I don't understand the ``and binaries'' part above.  Surely, you
meant to submit source-level diffs, no?

> I'm asking this because the changes seem to be small. May I stumble in a
> wall. . .

They are small, but they touch a very sensitive place in debug
support: exceptions, memory protection, etc.  Caveat emptor...