Mail Archives: djgpp/1997/06/09/09:05:47
J.A. Bijsterbosch wrote:
>
> As an IDE I'm using Rhide at the moment, because my previous experience was
> with Turbo C++ 3.0 for Dos. It works allright in textmode, but debugging
> some sources made with allegro the program crashes while debugging. (I
> know, it's
> in the docs ;-)). At that moment I thought to try another debugger that
> came within the djgpp package FSDB. However after a few tracing steps
As Eli already said, switching back from RHIDE to any of the other
debugger is in most (not in all) case meaningless, becuase the
debugger in RHIDE has already fixed many bugs which the other debuggers
still have (but recomiling these debuggers with the patches which
are part of the RHIDE source would fix them also in most situations).
As you have already read it, debugging programs which uses program
directly the hardware or use interrupt vectors is very hard and
not stable.
So here some hints:
- Get the newest RHIDE version (currently 1.2c)
- Try the '-G 1' switch when starting RHIDE
- Do NEVER use the autodetect feature of allegro when
debugging. RHIDE knows only about the VESA modes and
the standard VGA modes. Any other graphics mode will
bring undefined results.
And for the next: PLEASE include in any report at least the
version of RHIDE you are using or use the bug-report feature
of RHIDE.
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 *
*****************************************************************
- Raw text -