This shows you the differences between two versions of the page.
— |
blog:pushbx:2022:0424_ldebugx_compatibility_tweaks_dosemu2_native_dpmi_bugfix [2022-04-24 14:35:32 +0200 Apr Sun] (current) ecm created |
||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ====== lDebugX compatibility tweaks, dosemu2 native DPMI bugfix ====== | ||
+ | |||
+ | After [[https:// | ||
+ | running a DPMI client in dosemu2 | ||
+ | on a hosteurope virtual server, | ||
+ | several changes were made to both | ||
+ | lDebugX and dosemu2. | ||
+ | dosemu2 got [[https:// | ||
+ | out of this. Or [[https:// | ||
+ | Or [[https:// | ||
+ | |||
+ | ===== ===== | ||
+ | |||
+ | lDebugX changes include: | ||
+ | |||
+ | * [[https:// | ||
+ | |||
+ | * [[https:// | ||
+ | |||
+ | * [[https:// | ||
+ | |||
+ | * [[https:// | ||
+ | |||
+ | This last one is mostly a convenience really. | ||
+ | It does open up an interesting possibility | ||
+ | when debugging lDDebugX using lDebugX: | ||
+ | if the outer lDebugX sets the option, | ||
+ | it will gain control when the inner | ||
+ | lDDebugX' | ||
+ | starts executing. | ||
+ | However, as the debuggee is technically running | ||
+ | in lDDebugX' | ||
+ | the debuggable debugger will set up | ||
+ | its own PM handlers. | ||
+ | That means that the outer lDebugX | ||
+ | cannot safely trace past | ||
+ | [[https:// | ||
+ | |||
+ | |||
+ | |||
+ | {{tag> | ||
+ | |||
+ | |||
+ | ~~DISCUSSION~~ | ||