Debugger suggestions

BippyM · 26 January 2019, 18:19

So i have been trying to get used to the debugger and wondered if the following is possible or could be implemented.

Using the DASM1 or DASM2 can it be possible to have the whole memory being disassembled, or a large chunk of it, and then scroll through, so if I want to disassemble from say $1200, I can scroll backwards and see what was before without having to type d xxxx
With the MEM1/MEM2 screens, have the memory scrollable, also how do I set the memory region I want to view in this tab?
Make it possible to click on the OUT1, OUT2, DASM1 with the mouse as opposed to pressing F1 etc

Is there any other documentation for the debugger besides what is on EAB?

BippyM · 26 January 2019, 18:31

Also when I type a command in the other views (s m memory address) it displays in the OUT1 view.. Is this correct?

Toni Wilen · 26 January 2019, 19:13

GUI debugger is unsupported. I am not going to improve it (I didn't even wrote it originally) because it needs total rewrite to not be mostly useless.

Only console debugger is supported (xx command)

BippyM · 26 January 2019, 19:37

If that's the case then maybe you should remove it! Just a thought

ross · 26 January 2019, 20:17

Quote:

Originally Posted by BippyM

If that's the case then maybe you should remove it! Just a thought

Not before a replacement is made, please.

I know that is unsupported and use the CLI version mostly.
But GUI version is of great aid when I need a fast view of various memory zones or setting flags, registers, memory and all the visual feature.

Toni Wilen · 26 January 2019, 20:28

Main missing requirement is some easy to use multi-window framework.

BippyM · 26 January 2019, 20:48

I'm completely with you, a decent GUI debugger would make debugging and development a million times faster and more intuitive.. Imagine being able to click a memory location and change it, have multiple windows with different events in each, that update in realtime while emulation is running (naturally it would slow emulation down).

Quote:

Originally Posted by ross

Not before a replacement is made, please.

I know that is unsupported and use the CLI version mostly.
But GUI version is of great aid when I need a fast view of various memory zones or setting flags, registers, memory and all the visual feature.

26 January 2019, 18:19	#1
BippyM Global Moderator Join Date: Nov 2001 Location: Derby, UK Age: 48 Posts: 9,355	Debugger suggestions So i have been trying to get used to the debugger and wondered if the following is possible or could be implemented. Using the DASM1 or DASM2 can it be possible to have the whole memory being disassembled, or a large chunk of it, and then scroll through, so if I want to disassemble from say $1200, I can scroll backwards and see what was before without having to type d xxxx With the MEM1/MEM2 screens, have the memory scrollable, also how do I set the memory region I want to view in this tab? Make it possible to click on the OUT1, OUT2, DASM1 with the mouse as opposed to pressing F1 etc Is there any other documentation for the debugger besides what is on EAB?

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Debugger updates (was: WinUAE Debugger HH PC history)	selco	support.WinUAE	8	14 March 2018 22:27
Suggestions	BippyM	project.Maptapper	51	24 August 2016 19:57
Suggestions	Leandro Jardim	support.WinUAE	1	14 August 2010 08:14
Some help / suggestions please	skote	New to Emulation or Amiga scene	8	30 April 2008 10:43
Suggestions	killergorilla	request.UAE Wishlist	7	09 September 2005 12:46

26 January 2019, 18:31	#2
BippyM Global Moderator Join Date: Nov 2001 Location: Derby, UK Age: 48 Posts: 9,355	Also when I type a command in the other views (s m memory address) it displays in the OUT1 view.. Is this correct?

26 January 2019, 19:13	#3
Toni Wilen WinUAE developer Join Date: Aug 2001 Location: Hämeenlinna/Finland Age: 49 Posts: 26,507	GUI debugger is unsupported. I am not going to improve it (I didn't even wrote it originally) because it needs total rewrite to not be mostly useless. Only console debugger is supported (xx command)

26 January 2019, 19:37	#4
BippyM Global Moderator Join Date: Nov 2001 Location: Derby, UK Age: 48 Posts: 9,355	If that's the case then maybe you should remove it! Just a thought

26 January 2019, 20:28	#6
Toni Wilen WinUAE developer Join Date: Aug 2001 Location: Hämeenlinna/Finland Age: 49 Posts: 26,507	Main missing requirement is some easy to use multi-window framework.

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)