TURBO'd app that hangs the QL on termination...
Posted: Wed Nov 01, 2017 1:45 pm
Hi everyone
I'm trying to track down a problem with one of my TURBO'd SB applications that always hangs the QL when it terminates.
Of course there are many program-specific factors that could be the cause, but without writing pages on the program in question, I wonder if the summary below might prompt some thoughts...
I CHARGE the program on QPC before transferring to the target QL
TURBO configuration is 'Structured', <64K (or > 64k), 0 Copied Windows, 8 (or 16) KB DATASPACE, 350 (or 512) bytes Stack
Target QL is equipped with QL-SD, 640KB RAM, Minerva 1.89 and Hermes, running TK2 v2.23 (or v2.26), LNG v2.11, Turbo TK (v3.34), HOTKEY v.something, THinG v.something-else plus a host of other custom extensions - all from ROM (actually, a custom made NV SRAM)
HOT_GO and _lngInit are invoked before two other needed extension are loaded from SDC (a heavily customised MEM driver, plus modified DIYTK TIMER ext.)
Program runs fine (invoked by EW or EX from SDC) until it terminates via STOP (no further executable code appears after here - just DEFinitions - as expected by the Structured paradigm)
The CON window remains visible and no further KB input is recognised (it's as if SB Job 0 Chan #0 has also been killed - even running as EX fails to allow further switching to SB #0)
My Hermes continues to blip upon further key presses - some more spectacular crashes I've experienced will kill this too, but not in this case.
i'm pretty sure that earlier versions of my program didn't exhibit this behaviour, but can't find any significant changes in the termination phase of the program since - its just gotten larger as I've added features. Also, other TURBO'd programs running with an identical environment (TK2, LNG, etc) and TURBO configuration terminate as expected.
Even if you haven't got ideas on what is causing the crash, I'd be interesting in how you might troubleshoot such a situation.
Thanks for any ideas (at all!)
M.
I'm trying to track down a problem with one of my TURBO'd SB applications that always hangs the QL when it terminates.
Of course there are many program-specific factors that could be the cause, but without writing pages on the program in question, I wonder if the summary below might prompt some thoughts...
I CHARGE the program on QPC before transferring to the target QL
TURBO configuration is 'Structured', <64K (or > 64k), 0 Copied Windows, 8 (or 16) KB DATASPACE, 350 (or 512) bytes Stack
Target QL is equipped with QL-SD, 640KB RAM, Minerva 1.89 and Hermes, running TK2 v2.23 (or v2.26), LNG v2.11, Turbo TK (v3.34), HOTKEY v.something, THinG v.something-else plus a host of other custom extensions - all from ROM (actually, a custom made NV SRAM)
HOT_GO and _lngInit are invoked before two other needed extension are loaded from SDC (a heavily customised MEM driver, plus modified DIYTK TIMER ext.)
Program runs fine (invoked by EW or EX from SDC) until it terminates via STOP (no further executable code appears after here - just DEFinitions - as expected by the Structured paradigm)
The CON window remains visible and no further KB input is recognised (it's as if SB Job 0 Chan #0 has also been killed - even running as EX fails to allow further switching to SB #0)
My Hermes continues to blip upon further key presses - some more spectacular crashes I've experienced will kill this too, but not in this case.
i'm pretty sure that earlier versions of my program didn't exhibit this behaviour, but can't find any significant changes in the termination phase of the program since - its just gotten larger as I've added features. Also, other TURBO'd programs running with an identical environment (TK2, LNG, etc) and TURBO configuration terminate as expected.
Even if you haven't got ideas on what is causing the crash, I'd be interesting in how you might troubleshoot such a situation.
Thanks for any ideas (at all!)
M.