20 May 2022, 22:30 | #1 |
Registered User
Join Date: Apr 2019
Location: UK
Posts: 172
|
WinUAE debugger command line
Is it possible to launch WinUAE from the command line straight into the debugger?
My current command line is winuae64 -config=A1200.uae -0 disk.adfand I have to be quick on the draw to hit Shift+F12 before the bootblock is read. I've tried both the -D command line option as well as the use_debugger=true config file option but neither seem to work. Perhaps I have misinterpreted them. The ideal workflow would be to pass a debugger script on the command line to f.ex set a watchpoint or 'fp' command Thanks for any advice. Version: WinUAE4910_x64 Last edited by hop; 20 May 2022 at 22:46. Reason: Version number |
23 September 2023, 15:28 | #2 |
German Translator
Join Date: Aug 2018
Location: Drübeck / Germany
Age: 49
Posts: 185
|
to open the the debugger from commandline there is the command -D
https://www.vware.at/winuaehelp/Comm...arameters.html but I believe this command was never supported? In my tests also with older WinUAE versions the WinUAE debugger never opens by start from commandline. One idea to open the debugger by start is the f-command. The f-command is usefull to found the first RAM-adress (eg. boot block) (f Step forward until PC in RAM ("boot block finder") If you want analyze the bootcode (bootloader) you can use the f-command. After a reset the Amiga is waiting in the ROM. If you now insert a disk, the bootprocess is starting. The f-command stops at the first RAM adress. "until PC in RAM". Now you can trace the bootcode step by step to analyze or modify the code. The f-command is a breakpoint command so you can also look with H the previous instructions. |
24 September 2023, 18:11 | #3 |
Registered User
Join Date: Apr 2019
Location: UK
Posts: 172
|
Thanks, I'll try that out.
|
24 September 2023, 18:39 | #4 |
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,515
|
use_debugger has always been disabled in WinUAE. Don't know why. Not sure if I want to enable it if there are too many config files that have it enabled and suddenly users are confused when trying next version..
"f" is better choice anyway if you want to debug disk booting. If you really want to debug what ROM does early, enable "One second reboot pause" and press debugger shortcut during the delay. |
24 September 2023, 19:06 | #5 |
Registered User
Join Date: Apr 2019
Location: UK
Posts: 172
|
Thanks Toni
|
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
Thread Tools | |
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
WinUAE Command Line Problem | mrv2k | support.WinUAE | 6 | 10 March 2021 16:35 |
WinUAE fa debugger command bug | jotd | support.WinUAE | 2 | 15 September 2018 18:19 |
Winuae command line help | synchro | support.WinUAE | 1 | 20 February 2012 02:20 |
Winuae command line - autostart? | zardoz | support.WinUAE | 5 | 14 August 2010 17:59 |
Command line WinUae? | resle | support.WinUAE | 1 | 02 December 2005 12:13 |
|
|