Ralf Reköndt writes:
>I have done several tests to find out, why Qmon doesn't work with my BOOT,
> i.e. does not pop up by a call respr(0).
>
> In fact, Qmon *does* work . . . as long as you do not have loaded qlib_bin
> (2910 bytes) and qlib_ext (1472 Bytes), both from the last Qlib v3.36
> package. They are essential to get Qlib v3.36 work.
>
> Has anyone made similar experiences and does someone know, why it is as it
> is?
>
> All done under QPC2.
Have you tried the all-in-one Qlib_sys instead of _ext and _bin? For the
test below I have Qlib_sys v3.35 loaded:
Im using Qmon 2.11. Havent used it for years as I use Jmon. Doing a
QMON
type 'g'
CALL RESPR(0)
hangs Job 0, but the rest of QPC2 is fine. Starting an Sbasic daughter job
and then doing QMON 0 coaxes debugging to continue in Job 0's channel#0.
The reason Qmon appears to hang (but you can always <break>) is that it is
waiting for some IO or an exception to start it off. Afaik, it has always
behaved like this.
Per
_______________________________________________
QL-Users Mailing List
http://www.q-v-d.demon.co.uk/smsqe.htm
