Mail Archives: djgpp/1997/12/10/12:18:01
HJohn M. Aldrich wrote:
>
> Calvin French wrote:
> >
> > 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:
>
> For your problem, there is good news and there is bad news. The good
> news is that there already exists a function in the DJGPP libc named
> __dpmi_set_debug_watchpoint(), which calls the DPMI function 0x0b00. It
> accepts a pointer to a given location in your program and installs a
> breakpoint at that location when the program is run under a debugger.
>
> The bad news is that, at least under gdb (which RHIDE's debugger is
> based on), this function appears to have no effect whatsoever. It is a
> valid DPMI 0.9 function, and never seems to return an error, but gdb
> doesn't like it.
>
> I'm not a guru, so I can't tell you any more. Perhaps one of the other
> DPMI gurus here knows the exact answer. :-)
>
> hth
>
> --
> ---------------------------------------------------------------------
> | John M. Aldrich |"Men rarely (if ever) manage to dream |
> | aka Fighteer I |up a god superior to themselves. Most |
> | mailto:fighteer AT cs DOT com |gods have the manners and morals of a |
> | http://www.cs.com/fighteer |spoiled child." - Lazarus Long |
> ---------------------------------------------------------------------
Hi,
I always quit rhide than gdb xxxx.exe and once I'm there I l(list) til
I find my line number then braak n ... run and wait. I've not tried it
from rhide I'm sure it can be done. I'm not too much of an explorer.
Ian.
- Raw text -