UI21DEB deBUGGER released | crappy and incrappy stuff (Announce)
> > "Will your TSR allow the debugger to single step into Int 21 without
> > causing a mess?" was kind of a trick question.
>
> I see. The optimal case of a post of yours is a tricky
> question, the other, also pretty frequent case, are just rude attacks
> without any relation to original topic
This isn't true, just as it won't be true to say all your posts are crap and some more crying.
> Cm wrote:
>
> > I probably won't ever use some program by DOS386
> > but I still prefer acceptable useless programs over crappy ones
>
> Interesting point. The fear or virii pushes people into the
> irrationality, when the irrationality is exhausted they move on into the
> absurdity, and when the absurdity is exhausted then ...
Do you plan on writing any virus soon? To fear the mass of DOS users or so?
> > It just calls Int21 between all instructions
>
> Excellent (RTFS)
If you prefer NASM source, mail me.
> > (you could avoid this by setting my own DEBUG fork's [NDebug's]
> > "assume InDOS" mode, but it's DEBUG's right to do that anyway)
>
> I'm not that sure about that.
Well it still is, especially in case of Int21.50 and Int21.51 which are reentrant in M[es]S-DOS. For Int21 character I/O, see below.
> In JDEBUG source I see 3 branches:
>
> * INT $21 console
> * BIOS console
> * INT $21 redirected
>
> And I'm very skeptical about both the INT $21 console: dropped in favor of
> BIOS if debugging DOS kernel ... but why not always ?
Well, because apparantly Japheth never used DEBUG's help command '?' when tracing DOS. I'm currently looking for more occurances of Int21 that have to be avoided during InDOS mode. (L's and W's DOS calls are obvious cases here. I'll add "Can't do this while InDOS" messages for these.)
> and the
> INT $21 redirect ... seems obsolete, no need to abuse DEBUG as an
> assembler anymore (maybe things were very different 20 years ago, heh
> ).
I don't know what exactly you mean by "Int21 console". If you mean functions 01h-0Ch, these are redirected through the PHT (RBIL JFT) too as mentioned in RBIL61.
> > Your reentrancy counter (vvreecnt) would be sufficient if the code
> really used
> > it (despite the machine halting [?] when it reaches 255).
>
> Any better ideas ? Set up a 256-bit counter providing a "sufficiently low"
> probability of overflow before the universe implodes ?
What about a 1-bit NUL counter which is never increased? That's probably as useful as your previous solution
> > Of course MS-DOS's usage of InDOS is not sufficient.
>
> Interesting.
Just as interesting as all the other bad crap (there's some good crap too..) Microsoft did. More interesting might be whether (E)DR-DOS and DOS-C duplicate this uncomfortable behaviour.
---
l
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