Forum > FV/Textmode IDE

DOS IDE Debugger

<< < (2/2)


--- Quote from: Dmitry24 on April 20, 2020, 04:31:29 pm ---Is MI Interface can be supported in DOS? It is possible to compile IDE for DOS with GDBMI option but this IDE even cannot start debugging and halts.
--- End quote ---

I can't see how. It would probably be more complex and fragile than the static library due to DOS being a single tasking operating system.

--- Quote from: Dmitry24 on April 20, 2020, 04:31:29 pm ---I just tried a standalone DOS debugger v.6.11 I was able to find within FPC packages (thank you for suggestion) but I'm not sure if it is working at all. When I try stepping it hangs always. At the same time there is at least some success with integrated libraries for the GDB v.7.7.1 but I cannot find their standalone version.

Could you please suggest where I can find a newer DOS version of the debugger for DOS? The libraries v.7.7.1 were generated somehow:

--- End quote ---

I'm not working with DOS, so I don't know. You could try whether FreeDOS comes with a newer version.

I figured out how to run the standalone GDB debugger and yes, it allows stepping normally (at least the available version 6.11) regardless the program complexity.

While FPC integrated debugger hangs on stepping the program as soon as current source file size is larger than several tens of KBytes (even if there is just a single instruction except comments).

Previously I specified wrongly. The threshold size for the bug is approx. 20 KBytes.

Then the question now is whether it's a fault of the static library or of the way the TextMode IDE uses it.

The static library is imported through %fpcdir%\packages\gdbint\src and the IDE's debugger interface is in %fpcdir%\packages\ide\fpdebug.pas. You could maybe try to write a simple debugger interface for the static library and test whether this works correctly. Maybe this way one can find out the problem on DOS.

I checked, and there are two unmerged gdbint revisions:  44471,44774

r44471 | pierre | 2020-03-31 22:49:17 +0200 (Tue, 31 Mar 2020) | 9 lines
Changed paths:
   M /trunk/packages/gdbint/src/gdbint.pp

  Try to fix problems for more recent GDB versions.
  Move GDB_NEW_UI macro def. to GDB_VER_GE_712
  to same GDB_VER_GE_712.
  Use stdio_filopen to create gdb_stdout and gdb_stderr
  if GDB_HAS_GET_STDIN macro is set.
r44774 | pierre | 2020-04-18 11:53:24 +0200 (Sat, 18 Apr 2020) | 4 lines
Changed paths:
   M /trunk/packages/gdbint/src/gdbint.pp

  * Fix compilation of gdbint unit for go32v2, should resolve bug report 36923.
    Replace cint type by longint (as gdbint unit does not use ctypes unit).

Finally I found out that changing DOS extender (cwsdpmi.exe of any version) to another one (hdpmi32.exe) resolved the problem (and FPC version does not matter at the moment).

AFAIK there are different issues regarding DOS exteneded memory usage on modern PC's. What run on one PC may fail on another. I'm afraid the real issue is too complex...


[0] Message Index

[*] Previous page

Go to full version