Mail Archives: djgpp/2000/03/29/18:44:13
In article <8bsuap$j9q$1 AT nets3 DOT rz DOT RWTH-Aachen DOT DE>,
broeker AT physik DOT rwth-aachen DOT de wrote:
>I don't know what that structure support does, but it should
*never*
>cause any difference in behaviour of FSDB if you use it or
>not. Especially since NASM, as you say, does not generate any
debug
>info at all. I.e. the only output it generates is raw code and
data,
>as far as FSDB is concerned. It should never make any
>difference how
I think so too. But then again, NASM's support of structures are
a bit unconventional. Here's a sample :
mov eax,[mydata+mytype.data1]
As you can see, NASM treats structures only as offsets. The
following code is invalid according to NASM :
mov eax,[mydata.data1]
I only get these kind of problems with FSDB.
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.
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, but the programs output
gone hairy.
* Sent from RemarQ http://www.remarq.com The Internet's Discussion Network *
The fastest and easiest way to search and participate in Usenet - Free!
- Raw text -