UI21DEB deBUGGER released | inreentrant mess (Announce)
Thanks. BTW, since the release up to now I found cca 72'537'637'325'994 bugs in UI21DEB, so NO, it's not (yet) state of the art
> Because your hook is inreentrant
This would be a criminal BUG because it was supposed to be reentry-safe
> and JDEBUG uses Int21 as long as the InDOS flag is not set.
> The traced Int21 call then probably returns into DEBUG
As long as I don't know exactly what magic/mess JDEBUG does on the INT and IRET instructions
> The solution is to set up a reentrant stack frame to get the flags
maybe true ... still, no idea why this should be better
> and set up your own "InUI21DEB" flag.
But I already have a reentrancy counter !!!
> If that is set when entering the handler, completely
> skip to where you chain to the old handler.
So skip the "hacks" ... but what does this change ? Or do I have JMP to original INT $21 instead of CALL'ing it to avoid the "mess" on return ?
---
This is a LOGITECH mouse driver, but some software expect here
the following string:*** This is Copyright 1983 Microsoft ***
Complete thread:
- UI21DEB deBUGGER rele | DGJPP's persistent ENOENT bugginess - DOS386, 20.02.2009, 05:53 (Announce)
- UI21DEB deBUGGER rele | DGJPP's persistent ENOENT bugginess - DOS386, 20.02.2009, 06:19
- UI21DEB deBUGGER rele | DGJPP's persistent ENOENT bugginess - ecm, 20.02.2009, 20:19
- UI21DEB deBUGGER rele | DGJPP's persistent ENOENT bugginess - DOS386, 24.02.2009, 06:02
- UI21DEB deBUGGER rele | DGJPP's persistent ENOENT bugginess - Laaca, 24.02.2009, 10:28
- UI21DEB deBUGGER rele | DGJPP's persistent ENOENT bugginess - rr, 24.02.2009, 21:43
- UI21DEB deBUGGER rele | DGJPP's persistent ENOENT bugginess - DOS386, 25.02.2009, 03:06
- UI21DEB deBUGGER rele | DGJPP's persistent ENOENT bugginess - ecm, 25.02.2009, 13:15
- UI21DEB deBUGGER rele | DGJPP's persistent ENOENT bugginess - DOS386, 25.02.2009, 03:06
- UI21DEB deBUGGER rele | DGJPP's persistent ENOENT bugginess - Japheth, 25.02.2009, 14:09
- UI21DEB deBUGGER released | the mess - DOS386, 01.03.2009, 08:24
- UI21DEB deBUGGER released | the mess - ecm, 01.03.2009, 10:40
- UI21DEB deBUGGER released | inreentrant mess - DOS386, 01.03.2009, 13:59
- UI21DEB deBUGGER released | inreentrant mess - ecm, 01.03.2009, 16:19
- UI21DEB deBUGGER released | inreentrant mess - Japheth, 02.03.2009, 07:48
- UI21DEB deBUGGER released | inreentrant mess - ecm, 02.03.2009, 15:28
- UI21DEB deBUGGER released | inreentrant mess - Japheth, 03.03.2009, 07:52
- UI21DEB deBUGGER released | crappy and incrappy stuff - DOS386, 15.03.2009, 02:39
- UI21DEB deBUGGER released | crappy and incrappy stuff - Japheth, 15.03.2009, 08:17
- UI21DEB deBUGGER released | crappy and incrappy stuff - ecm, 15.03.2009, 21:02
- UI21DEB deBUGGER released | inreentrant mess - ecm, 02.03.2009, 15:28
- UI21DEB deBUGGER released | inreentrant mess - DOS386, 01.03.2009, 13:59
- UI21DEB deBUGGER released | the mess - ecm, 01.03.2009, 10:40
- UI21DEB deBUGGER released | the mess - DOS386, 01.03.2009, 08:24
- UI21DEB deBUGGER rele | DGJPP's persistent ENOENT bugginess - DOS386, 24.02.2009, 06:02
- UI21DEB deBUGGER rele | DGJPP's persistent ENOENT bugginess - Laaca, 20.02.2009, 20:21
- UI21DEB deBUGGER rele | DGJPP's persistent ENOENT bugginess - ecm, 20.02.2009, 20:19
- UI21DEB deBUGGER rele | DGJPP's persistent ENOENT bugginess - DOS386, 20.02.2009, 06:19