eteran
Stack display: logarithmic scrolling
It should highlight different stack frames with different background colors, so that you easily see which things belong to which function. Or draw separating lines between the frames. Similar everything after $esp should be grayed out a little bit.
It is also confusing that the addresses in the data display run down, but in the stack display up.
And the scrollbars appear to be are next to useless, because the address range is so large that a simple dragging moves you far, far away. You could try to use some sort of log scale scrollbar whose initial scrolling speed is slow, but becomes increasingly fast when the distance of the handle to its original position increases.
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
There are a few things here, so they'll be addressed individually:
It should highlight different stack frames with different background colors, so
that you easily see which things belong to which function.
Or draw separating lines between the frames.
Cool Idea, I like it.
Similar everything after $esp should be grayed out a little bit.
Done
It is also confusing that the addresses in the data display run down, but in
the stack display up.
Probably won't fix this, at least not by default. edb is following the convention established by pretty much every other debugger I've worked with. Perhaps it's worth making it an option at some point, but honestly, it'll be relatively low priority.
And the scrollbars appear to be are next to useless, because the address range
is so large that a simple dragging moves you far, far away.
You could try to use some sort of log scale scrollbar whose initial scrolling
speed is slow, but becomes increasingly fast when the distance of the handle to
its original position increases.
Not a bad idea, I'll have to think about how to best implement such a thing, but it's doable.
Hmm, do addresses really decrease as you go down in stack view? As I checked, it's consistent with data view. Am I confusing something?
Heh, no they don't :-P. Either way, the current status of that part is "works like every other debugger, so won't fix"
So this bug currently basically boils down to two issues worth discussion:
- logarithmic scrolling for large data/stack regions
- stack frame outlining.
The second is a effectively dupe of issue #52.
So the only remaining item here is the first. I am going to rename the issue accordingly.