Benjamin Landers

It would be an option to make the value of medeleg a setting. Alternatively it could perhaps be a register you can see in the window, but not access from...

Thanks for taking a stab at implementing this. Some minor problems: - `medeleg` doesn't have any hint text. - trying to read `medeleg` should throw an illegal instruction exception -...

It seems like no progress is currently being made on this. I plan to address the problems myself. I plan to make a new class of register that is only...

You should be able to specify a range to dump when using the command interface. I don't think that feature is documented or tested anywhere though. I just tested it...

I am not sure what an ideal way to offer that option in the GUI is. The easy way would be to add a `.text + .data` option, but I...

I would be inclined to go with something like option 1. I'll check out the code you have in your fork over the weekend.

I took a look, and I would not have implemented the change the way you did. It adds a lot of boilerplate code to each dump. Additionally it has different...

>> My preferred solution would modify the dumped ranges before actually passing it to the individual dump and remove the getRawWordOrNull checks > I am changing the memory ranges passed...

> Do you have any feedback on the implementation of defining the "both" memory range? I didn't like using hardcoded index numbers, but wasn't sure of a better approach. Your...

> Under the default memory configuration, the size / location of .text and .data make the resulting file absurdly large under most formats. There is a definite UI freeze as...