Forum > Debugger
CPU-View
Alexander (Rouse_) Bagel:
I do reverse engineering, and I miss the capabilities of the regular FpDebug debugger.
Today I want to show my work that I've been doing for almost a year to make the debugger better. It's not finished yet, it needs a lot of tweaks, but I need someone to look at it.
It's a full GUI debugger with a lot of supported features. I've implemented in it what I was missing. I think it makes sense to add many of my solutions to the main debugger.
CPU-View is under development and I make changes to it every day, I miss the opinion of specialists who are immersed in this task (it's not application level - it should really be system engineers).
There are not enough IOTA interfaces, all debugging is laid directly on specific windows. If they let me - I could offer my implementation.
https://github.com/AlexanderBagel/CPUView
Martin_fr:
Looks great.
I'll have to finish a few things right now, but I will have a look asap.
I would be happy to help integrate most of this with the IDE. Though probably keeping the asm,reg,dump windows as separate (but anyone with anchordock can combine them).
One thing that may be a bit more complicated (unless you already have something / I haven't looked) is the register view. The Problem is that there are different CPUs supported. (We have the remote arm, and Mac M1/2/3, and with gdb even more).
So there will be a need for a generic and for cpu specific reg-windows (or for backends to provide display info).
Also I haven't checked on what you done on the interface between frontend and backend. I will comment on that as soon as I had a chance to look through it.
In any case thanks for all the work, and sharing it here.
---
Btw, we now have 2 mem-dump viewers, since I added one too.
As for the interfaces => there are definite needs to create some. Except for the watches the entire front/backend api is legacy (from when there was only one debugger, no front, no back-end).
But as I said details on that to follow.
Alexander (Rouse_) Bagel:
Yes, MemViewer - it has helped me more than once, thank you very much am for putting it into debugging.
Well, as for registers - I've done a lot of work to isolate them into an abstraction and separate them into a separate data model. Therefore, registers in the debugger can be represented as they are implemented by the current processor. It doesn't matter Intel/Arm/Z80 or otherwise.
Fibonacci:
During my short playtime with it, it crashed twice and froze once
Alexander (Rouse_) Bagel:
--- Quote from: Fibonacci on October 20, 2024, 10:18:00 am ---During my short playtime with it, it crashed twice and froze once
--- End quote ---
Got it. I'll check it, apparently I forgot to check synchronization somewhere, which can cause hangs. And something with the dictionaries.
Navigation
[0] Message Index
[#] Next page