From: Robert Hoehne <rhoehne AT mathematik DOT tu-chemnitz DOT de>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: rhide bug
Date: Fri, 29 Aug 1997 14:26:32 +0200
Organization: University of Technology Chemnitz, FRG
Lines: 51
Message-ID: <Pine.HPP.3.95q.970829141018.28479A-100000@newton.mathematik.tu-chemnitz.de>
References: <34001A31 DOT 3674 AT wanadoo DOT fr> <34056467 DOT 305629E6 AT Mathematik DOT TU-Chemnitz DOT DE> <Pine DOT GSO DOT 3 DOT 95 DOT 970829014422 DOT 4265E-100000 AT dilbert DOT ucdavis DOT edu>
NNTP-Posting-Host: newton.mathematik.tu-chemnitz.de
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <Pine.GSO.3.95.970829014422.4265E-100000@dilbert.ucdavis.edu>
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

On Fri, 29 Aug 1997, Mike Darrett wrote:

> 	Sometimes when I press <Ctrl-C> in Rhide, either the editor
> crashes or it says something like "Do you really want to interrupt
> Rhide?". Is this normal? I'm used to pressing like Ctrl-KB, Ctrl-KK,
> Ctrl-KC, and this happened to me several times while I was working on my
> project. 

Yes, this is normal. If you think a little bit I hope you
agree with me. Ctrl-C is as far as I remember in any commonly
used OS the interrupt key and so RHIDE handles now also Ctrl-C.

In my opinion the correct usage of the Ctrl-K-.. and Ctrl-Q-..
combinations is to press Ctrl-K (or Q) the releasing the Ctrl key
and then pressing the second character.

I will probably not change this behaviour in the future, but
maybe SET will do it in the editor by recognising the first
Ctrl-K (or Q) key, and then temporary disabling SIGINT for the
next key.

> p.s. How did such a bug as the 25 floating point divisions EXIST? (It
> was fun tho =)

Until you don't know about the RHIDE internals (especially how
it communicates with the builtin GDB) and my tricks to reduce
the executable size the description would not fit in this group.

Theoretical this the same thing, like a common bug in mostly
any application to dereference a NULL pointer but here with
an other result.

And BTW: The zero-dividing error is only produced by RHIDE
itself to force a crash and so a traceback when something
where wrong internally in RHIDE. That means the original
bug has nothing to do with "Division by Zero". If you would
have redirected stderr to file when running RHIDE to produce
the crash and then looking in that file, you would have seen,
that there is printed something like

"RHIDE internal error" together with the wish to send me the
produced error file.

Robert
*****************************************************************
* Robert Hoehne, Fakultaet fuer Mathematik, TU-Chemnitz-Zwickau *
* Post:    Am Berg 3, D-09573 Dittmannsdorf                     *
* e-Mail:  Robert DOT Hoehne AT Mathematik DOT TU-Chemnitz DOT DE              *
* WWW:     http://www.tu-chemnitz.de/~rho                       *
*****************************************************************