# Tutorial:How to break into a running Clarion app with the Debugger. - open for criticism & suggestions **URL:** \ **Category:** tips\ **Tags:** debugger, github\ **Created:** [July 28, 2025, 9:00pm UTC](https://clarionhub.com/t/tutorial-how-to-break-into-a-running-clarion-app-with-the-debugger-open-for-criticism-suggestions/8430 "2025-07-28T21:00:56Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![RchdR](https://clarionhub.com/letter_avatar_proxy/v4/letter/r/d78d45/32.png) [@RchdR](https://clarionhub.com/u/RchdR)\ **Post date:** [July 28, 2025, 9:00pm UTC](https://clarionhub.com/t/tutorial-how-to-break-into-a-running-clarion-app-with-the-debugger-open-for-criticism-suggestions/8430/1 "2025-07-28T21:00:56Z")
Comments welcome, hope you find it useful if you didnt know about this. > **[GitHub - Intelligent-Silicon/Call-Clarion-Debugger-from-running-App](https://github.com/Intelligent-Silicon/Call-Clarion-Debugger-from-running-App)** > > Contribute to Intelligent-Silicon/Call-Clarion-Debugger-from-running-App development by creating an account on GitHub. ---
**Author:** ![ironmansculler](https://clarionhub.com/user_avatar/clarionhub.com/ironmansculler/32/5421_2.png) [@ironmansculler](https://clarionhub.com/u/ironmansculler)\ **Post date:** [July 28, 2025, 9:29pm UTC](https://clarionhub.com/t/tutorial-how-to-break-into-a-running-clarion-app-with-the-debugger-open-for-criticism-suggestions/8430/2 "2025-07-28T21:29:09Z")
well done… flow it into claude code and claude desktop and generate template code to implement it in embed points? certainly a great example. ---
**Author:** ![RchdR](https://clarionhub.com/letter_avatar_proxy/v4/letter/r/d78d45/32.png) [@RchdR](https://clarionhub.com/u/RchdR)\ **Post date:** [July 29, 2025, 6:12am UTC](https://clarionhub.com/t/tutorial-how-to-break-into-a-running-clarion-app-with-the-debugger-open-for-criticism-suggestions/8430/3 "2025-07-29T06:12:35Z")
No need, I think Capesoft have a template called BreakIn. > **[CapeSoft BreakIn](https://www.capesoft.com/accessories/breakinsp.htm)** My template would create a hotkey on every (window) procedure, which in turn calls an Assert(), and thus break in to the app using the debugger and processid. My example just calls the debugger using the PID, so I expect @Bruce or @Vitesse will incorporate the cladb -p into BreakIn. ---
**Author:** ![Bruce](https://clarionhub.com/letter_avatar_proxy/v4/letter/b/ccd318/32.png) [@Bruce](https://clarionhub.com/u/Bruce)\ **Post date:** [July 29, 2025, 6:36am UTC](https://clarionhub.com/t/tutorial-how-to-break-into-a-running-clarion-app-with-the-debugger-open-for-criticism-suggestions/8430/4 "2025-07-29T06:36:07Z")
Well I’m pretty sure Geoff Robinson won’t be doing it 🙂 - I think maybe you’re thinking of Geoff Thomson, which is someone quite different. I’m also not really sure what incorporating cladb into BreakIn would do. BreakIn is for observing where in the code each thread is, and I’m not sure jumping over to the debugger would do any good. ---
**Author:** ![RchdR](https://clarionhub.com/letter_avatar_proxy/v4/letter/r/d78d45/32.png) [@RchdR](https://clarionhub.com/u/RchdR)\ **Post date:** [July 29, 2025, 7:57am UTC](https://clarionhub.com/t/tutorial-how-to-break-into-a-running-clarion-app-with-the-debugger-open-for-criticism-suggestions/8430/5 "2025-07-29T07:57:56Z")
I thought @vitesse did work for you. Not to worry. Anyway, I’ve just added another example: Example7AppGenAssert. > **[GitHub - Intelligent-Silicon/Call-Clarion-Debugger-from-running-App](https://github.com/Intelligent-Silicon/Call-Clarion-Debugger-from-running-App?tab=readme-ov-file#example7appgenassert)** > > Contribute to Intelligent-Silicon/Call-Clarion-Debugger-from-running-App development by creating an account on GitHub. Shows how to use an Alert key (CtrlD) in an AppGen procedure to trigger an Assert and in turn call the Debugger to step into it. Now this could be templatised easily. ---
**Author:** ![RchdR](https://clarionhub.com/letter_avatar_proxy/v4/letter/r/d78d45/32.png) [@RchdR](https://clarionhub.com/u/RchdR)\ **Post date:** [July 29, 2025, 9:47pm UTC](https://clarionhub.com/t/tutorial-how-to-break-into-a-running-clarion-app-with-the-debugger-open-for-criticism-suggestions/8430/6 "2025-07-29T21:47:30Z")
Screenshots of the template which provides reasonable flexibility for ABC and CW20 (Clarion) template family. (any other template families?) Global template, cascades settings to every Browse, Form, Process (non source code) procedure template. Each Procedure template can be individually disabled or reconfigured. Cant think of anything else to add to the template at this stage, but if anyone has suggestions, let me know and I’ll probably include it. General Tab ![General Tab](https://clarionhub-uploads.s3.eu-north-1.amazonaws.com/original/2X/3/3ea27b15ece2971a6ed23355e70d35ca80d516ed.png) Debugger Properties Tab ![Debugger Properties Tab](https://clarionhub-uploads.s3.eu-north-1.amazonaws.com/original/2X/8/8ae860cf3a8700c7255aff4e9b0816073c80773b.png) Debugger Procedure Call Code ![Debugger Procedure Code](https://clarionhub-uploads.s3.eu-north-1.amazonaws.com/original/2X/2/212ccc12837a261517a7b1efe564294156a904c6.png) A C6 version will follow as it involves rescaling/repositioning template controls for the reduced width.