Mail Archives: djgpp/1998/04/20/07:31:43
> >Okay now, I have been using the DJGPP compiler with rhide ever since I
> >downloaded DJGPP. Nothing has failed me, (but then again, no really big
> >programs...) I am wrtting this game, and in order to load up some data, I
> >need to store it in a file of record. (or structers...) Now, I have written
> >3 demo programs to see why MOST of the time Rhide crashes. I thought it was
> >from me, and maybe I was making some little syntax
> >mistake. No, it doesn't appear that way. I am getting every frustrated with
> >this, but I am asking for some assistance. Here are are 2 programs I have
> >written, to test rhide and see if it is ride it self or if its djgpp.
> >Most of the time they DON'T work, but if I run the same program 2 times in
> >a row, it works fine... :(
> >
I didn't look at the code but the message suggests you are getting
segment violations. When a program does faulty memory writes in
Rhide a lot of the time it overwrites memory alocated to rhide
so the violation doesn't get flaged where it happens.
If you compile with debugging on, drop out of rhide and run
the program from the command line. If it crashes with a SIGSEV
message, while the message is still on the screen type
symify -the full name of the program-
you should get a printout of where in the code the problem is.
Rhide is pretty well bug free at the level of just running
simple programs, but it doesn't protect itself from code bugs.
Another option if you have code thats trashing Rhide is to use
the GDB debugger on the command line, you probably have it with
the download packages. Type dgb and once its running enter
a question mark, to get the command options.
Charles Terry
- Raw text -