Back to home page

DOS ain't dead

Forum index page

Log in | Register

Back to the forum
Board view  Mix view

UI21DEB deBUGGER released | inreentrant mess (Announce)

posted by ecm Homepage E-mail, Düsseldorf, Germany, 02.03.2009, 15:28

> > > Because your hook is inreentrant
> >
> > This would be a criminal BUG because it was supposed to be reentry-safe
> > :crying:
>
> Please calm down! "Will your TSR allow the debugger to single step into
> Int 21 without causing a mess?" was kind of a trick question. Correct
> answer is "No", but it's half of the truth only, the fully correct answer
> is "No, and I don't care at all, because it's your crappy debugger which
> is faulty" :-D

I rather expected this because of the question, but don't approve your intention. Well, yes, I probably won't ever use some program by DOS386, but I still prefer acceptable useless programs over crappy ones ;-)

> The reason is simple: your code clears IF, which is a hint for any
> debugger that a critical section is entered which isn't allowed to be
> interrupted. The problem is that all DEBUGs ignore this signal - they
> aren't designed to debug "low-level" code.

IF is often meaningless if any form of multitasking is running.

> You can make your code more tolerant by implementing Christian's
> stack frame solution, but it's probably not worth the effort.

The problem here is that even "normal" TSRs (not DEBUG) might want to use DOS functions reentrant in MS-DOS. Even the Int24 handler of COMMAND.COM might crash UI21DEB, because it (is allowed to and) calls some low functions (01h-0Ch) during another Int21 call.

---
l

 

Complete thread:

Back to the forum
Board view  Mix view
22632 Postings in 2109 Threads, 402 registered users, 421 users online (0 registered, 421 guests)
DOS ain't dead | Admin contact
RSS Feed
powered by my little forum