Mail Archives: djgpp/1997/12/09/15:02:09
Newsgroups: | comp.os.msdos.djgpp
|
Subject: | RHIDE Debugging Idea...
|
From: | frenchc AT cadvision DOT com (Calvin French)
|
MIME-Version: | 1.0
|
NNTP-Posting-Host: | ts5ip185.cadvision.com
|
Message-ID: | <348d87d3.0@news.cadvision.com>
|
Date: | 9 Dec 97 18:02:59 GMT
|
Lines: | 41
|
Organization: | CADVision Development Corporation (http://www.cadvision.com/)
|
To: | djgpp AT delorie DOT com
|
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp
|
Hi, I have an idea which would be extremely useful and convenient for
debugging with RHIDE. Let me give tell you how I accomplish this now, then
you will understand my suggestion. Basically, within the main loop of my
code, or somewhere I have something like this (I am making an Allegro
program):
if( key[ KEY_SPACE ] )
{
int a = 0;
};
And that's all. Then what I do, is set a breakpoint on the line, int a = 0.
Then, I can run my program until a peculiar behavior occurs, at which point I
can just press space, and then debug effectively. Now, this approach works
fine, the only problem being that when I clear breakpoints I have to re-set
this one. It is just a bit inconvenient. So what I really want to know is if
there is an interrupt or something else I can pull to cause RHIDE to behave
as if it just hit a breakpoint. Then, I could do something like:
#include "breaks.h"
...
if( key[ KEY_SPACE ] ) breakpoint();
Perhaps there is already a way to do this, or perhaps it is not even
possible/not worth the effort. I really have no idea. At any rate, could
somebody more knowledgable fill me in? If this could be accomplished, it
would then become relatively simple to take it one step further, and:
#include "breaks.h"
...
install_break_handler( KEY_BREAK );
The handler being triggered by some key, say the PAUSE/BREAK key. This would
be really quite useful.
- Calvin -
- Raw text -