Gecko dotNET Bugs and Requests

[Romaap]

Something I was thinking about is like a "Step To" or "Log Steps", which would step into until it has reached a specified address (or until the user cancels it) and everything is logged.
The log could contain at least the instructions executed, and maybe the values of the registers used.
Also maybe making something like:

80151A8E0 Start
80151A908 branch to 80138F20
     80138F20 start of subroutine 1
     80138F34 branch to 802A8380
          802A8380 start of subroutine 2
          802A83F4 end of subroutine 2
     80138F6C end of subroutine 1
80151A940 end


but it wont be really necessary ;)


Oh and I guess I found a bug?
In the one line assembler I can't change something to "blr", so I have to poke it with 4E800020 every time.

[James0x57]

I might make a Mask field to do this, so we get the bit-level resolution.

That would be awesome!

Just want to second that blr thing, can't assemble them either.

[dcx2]

wiiztec has asked for logging before, but I like the idea of indenting function calls and echoing register contents.  He has also mentioned Step until the Breakpoint conditions are satisfied; this could be an option in the Step Until... dialog box.  This would be a somewhat lengthy adventure so it might be a while before such a feature shows up.

Regarding blr, I think I noticed the assembler throwing a hissy fit when I tried to put in bctrl.  I'll look into this.

[wiiztec]

Could you move show mem to that vacant spot in the step group often one would press show mem after stepping so it would make sense for them to be close together,

also if you squeezed the registers a little closer togehter and maybe just make Gecko.NET as a whole a tiny bit longer you could use that space where show mem used to be for the active conditions textbox (you could put "skipped" beside the "step" that denotes the step button group (it is related after all))

[dcx2]

Could you move show mem to that vacant spot in the step group often one would press show mem after stepping so it would make sense for them to be close together,

Step Until is probably going to go in that blank spot.  It will have two functions that you choose from a popup; it will repeatedly Step Into until a specified register is used as a destination or source, or Step Into until the Breakpoint Conditions are satisfied (you asked for this earlier).

also if you squeezed the registers a little closer togehter and maybe just make Gecko.NET as a whole a tiny bit longer you could use that space where show mem used to be for the active conditions textbox (you could put "skipped" beside the "step" that denotes the step button group (it is related after all))

I'll consider moving Show Mem up to the top beside the Step box, and perhaps Delete/Clear so that they're above the Breakpoint Conditions.

[wiiztec]

How about something like this?

[James0x57]

lmao

[James0x57]

Thanks for all the work on this man, much appreciated. =)

Another Request:
A search option to swap between signed/unsigned comparisons on the type (8/16/32/Single Float).

[dcx2]

I am already considering a multi-level Undo with a complete history that optionally will add extra columns to the search result ListView for each level, so you can see every search result there ever was.  I mentioned this back in my "what do I have planned?" post, at the top of page 7 of this thread.

I am also considering looking for a + or - in front of the search value as an indication of a signed search.  No + or - would indicate an unsigned search.

FYI, there won't be much motion on this for a week or two.  I might do some rearranging of the Breakpoint tab, because that's quick and easy and wiiztec gave me a few ideas.  Eventually, though, I'd like to rev up to 0.62.

[James0x57]

Repeatable Bug: If USB Gecko disconnects, you can't restart the search when you re-connect (the button is greyed out).


Request: In unknown searches, "equal to old value" would rock my socks. ;)


Good luck with whatever's got you busy on the outside!

[dcx2]

I'll look into the button greyed out thing.  If any buttons get greyed out and they shouldn't be, pressing the Reconnect button should fix it.

Not sure what you mean by "unknown equal to old value".  On an unknown search (which is only the first search), there is no old value.  After your first unknown search, you're comparing against last value.  And we do have "equal to last value".

[James0x57]

Yeah, I don't know why I specified the start type search. Anyway, Equal to last is comparing the "New" value in the search history. If there was one that compared to the "Old" value that would be awesome.

[dcx2]

Ah, okay, I kind of see where you're going.

This ties in somewhat with the multi-level undo.  I was also considering adding "first" to "last" and "specific".

[Romaap]

I was thinking about something like an auto-poke.
Like you start autopoke like you would with multipoke, but it just pokes the first address then 1 second later it pokes the second address and 1 second later it pokes the third etc.

It could be a popup with options like what value to poke and if it should repeat after the last address, set the delay and maybe like if the value should be increased with every poke/after last address is poked.
And like a Start button, a Stop button, a Pause button and a Step button?



Edit: Also something I would love to have is keyboard shortcuts for Step into, Step out and Step over.

[wiiztec]

The text view of the registers is screwed up in r75 also there's an unnecessary horizontal scrollbar at the bottom of edit view