Mail Archives: djgpp/1998/08/10/05:19:53
From: Endlisnis <s257m AT unb DOT ca>
Subject: Bug in RHIDE 1.4.5
To: djgpp AT delorie DOT com
I'm using patched version of RHIDE-1.4.5 built together with
sources of gdb-4.16 (instead of 4.17)
> I recently upgraded from RHIDE v1.4 to v1.4.5 and have found some odd
> things (bugs?). I had many problems trying to use the old project files,
> rhide kept crashing [printing 1000's of different error messages].
I haven't seen anything like. However project files touched with
1.4.5 are no more usable with 1.4
> I re-did all of my project files and that worked. But now it can't debug
> anything complex. If I try and write something simple, it debugs fine, but
> any program I tried it on that was reasonably large (100+ lines of code)
> pressing 'F8' (or using the menu selection) ran the entire program, not
> just the line.
Known problem with original binaries. Use them to rebuild rhide-
1.4.5 from sources with libgdb from gdb-4.16 instead of 4.17.
Some hacking may be needed.
> I made the smallest version of a file that didn't work, I
> redirected 'stdout' into rhide and what I got is at the end of the
> message. I have also included the code that made this happen. I think I
> will move back to v1.4 for now, I would like to use 1.4.5 if there is a way
> to avoid this (or it can be fixed).
> =====================File that screws up debugger
> #include<iostream.h>
> #include<string.h>
> #include<dpmi.h>
>
> void Mode(short M)
> {
> __dpmi_regs Regs;
>
> memset(&Regs, 0, sizeof(Regs));
> Regs.x.ax = M;
> __dpmi_int(0x10, &Regs);
> }
>
>
> int main()
> {
> Mode(0x13);
> cout << "Hi!";
> Mode(0x3);
> return 0;
> }
No crashes for me with patched 1.4.5. However I don't see output
in mode 0x13. I think that can also crash on different video card
as RHIDE does not handle 256 color modes well.
- Raw text -