Hatari debugger

[SToS]

I have searched this forum and performed a general internet search for the answer to this but to no avail.

Why has Hatari debugger got no search/find in memory or mnemonic functionality?

I find this a basic action that most if not all debuggers usually have, or am I missing something?

Before I go poking around/hacking my own solution in the source code, does anyone know better?

Thanks.

[troed]

I agree that would be welcome functionality. On the note on Hatari and debugging, you might want to look into hrdb if you haven't already: http://clarets.org/steve/projects/hrdb.html

[TheNameOfTheGame]

Eero was telling me that Hatari no longer needs SDL1 and SDL2 supports more than one window.

Might be time to get a debugger gui windowing system built-in to Hatari? Hatari already has so many debugger capabilities built-in, just have to get them available in a window.

Hrdb is well done and tat is a good guy, but it is really built for remote debugging and it works well for that, but has limitations due to it's primary mission. Having a gui built-in to Hatari would be the perfect answer.

[SToS]

I agree that would be welcome functionality. On the note on Hatari and debugging, you might want to look into hrdb if you haven't already: http://clarets.org/steve/projects/hrdb.html

Thanks. I'll take a look.

[thomas3]

I have searched this forum and performed a general internet search for the answer to this but to no avail.

Why has Hatari debugger got no search/find in memory or mnemonic functionality?

I find this a basic action that most if not all debuggers usually have, or am I missing something?

Before I go poking around/hacking my own solution in the source code, does anyone know better?

Thanks.

Steem boiler room/debug has this function

[SToS]

Steem boiler room/debug has this function

Thanks thomas3, but not a Windows user and I wouldn't have the "power" to run an emulator under Wine under Linux.
I've not touched Windows since XP, but I do remember STeem (debug version) being very good though.

I think I'll take a look at the Hatari source code this weekend and see what I can come up with, if not I'll keep using xxd and grep for now.

Thanks again.

[tat]

Sorry, yes, hrdb has a search facility for hex or text strings. Hit Ctrl+F when you are in a Memory Window. I failed to add it in the instructions.

[Eero Tamminen]

Why has Hatari debugger got no search/find in memory or mnemonic functionality?

I find this a basic action that most if not all debuggers usually have, or am I missing something?

It's been on TODO list, but nobody's had time to implement it yet. I don't remember anybody specifically asking for it either though.

Could you describe how exactly you think search functionality should work (in regards e.g. to quoting, repeating search etc)?

[SToS]

It's been on TODO list, but nobody's had time to implement it yet. I don't remember anybody specifically asking for it either though.

Could you describe how exactly you think search functionality should work (in regards e.g. to quoting, repeating search etc)?

Completely off the top of my head.

Keeping inline with the current format of commands maybe...

memfind (mf) [b|w|l|s] start_address length/end_address value1 [value2 ...]
b|w|l = usual byte|word|long
s = string

Length or End address? Not sure? Maybe prefix with + for length maybe.

It would probably make sense to limit the search value to 1 if it is a string search request.

Or just allow quoted characters for values using a byte (b) search?

As for repeat search, I think just finding and displaying ALL matches within the parameters defined is enough.

[Eero Tamminen]

memfind (mf) [b|w|l|s] start_address length/end_address value1 [value2 ...]

Took a bit longer than I thought until I got time for this (=vacation), but change series implementing "find" command is now commited to git: https://git.tuxfamily.org/hatari/hatari.git/log/

(Handling character locale transitions between Atari and host required some additional work.)

As for repeat search, I think just finding and displaying ALL matches within the parameters defined is enough.

It has simple pager that waits user input after each "page" of output.

(By default, page = how much fits into terminal, when one has built Hatari with readline support.)