Hi,
Just found zerobugs today, it's a great tool. I played with it a
little bit, here are some suggestions:
1) GUI layout:
http://www.zero-bugs.com/images/suse.png
I think the most important info I want to see when my program crash
are:
-- source code
-- stack trace
-- my local variables (not registers, just as zerobugs is intended as
an application debugger, not a kernel debugger)
So I hope the default layout show the local variable value instead of
register value; right now, when I change the stack frame I want to
exam, I need to an extra click to see the local variable tab.
Also I'd like the 3 windows layout like this:
================= | |
| |
| |
| |
| |
| |
================= | |
| |
================= | |
The reason is that when people exam variable values, he need to expand
the variable tree, we should give variable window more vertical space.
And function names (in the stack window) is typically the same width
as the code itself.
I hope you are convinced of my arguments; if not, at least make every
window dockable, so I can re-arrange the widow the way I like it
(currently I can't).
2) command line interface: why not simulate the gdb convention:
-- treat 'return' as repeat last command
-- use short names, e.g. 'p' is same as 'print', 'n' as 'next'
This will save lots of typing.