Mail Archives: djgpp/2000/03/31/20:24:05
> BTW, I tried using RHIDE/RHGDB. The problem now is when invoking
> int 0x31 function 0x300, RHIDE/RHGDB jumps to what I suspect is
> an exception handler, then it crashed because dual/triple fault.
As I wrote in another message, stepping through Int instructions is
tricky. If the problem happens when you step through Int NN
instructions, it probably happens because the version of RHIDE you are
using was built with an old version of GDB.
You should stil be able to set a breakpoint *after* the Int NN
instruction and "continue" the program, instead of stepping. After it
hits the breakpoint, step as usual.
> Another problem is when I define a structure in the ASM modules,
> when I use 'p' in gdb it indicates that the structure is a
> variable that cannot taken/printed by components. If I define it
> in C module, the 'p' command runs fine
The information about the layout of complex data structures is not
something that's magically known to the debugger: it is the
responsibility of the compiler/assembler to produce it. Since NASM
doesn't support COFF debugging info, GDB cannot know how to interpret
the variable.
> but the programs output gone hairy.
Hmm? What do you mean by this, exactly.
- Raw text -