New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The usual gdb commands abbreviations should work #7
Comments
Hmm.... It looks like I've been using the wrong abbreviations for "up" and "down" for a very long time! For me and the other debuggers, this is bad news. I'll change it in Devel::Trepan and will start to make the migration elsewhere (which means I may need to take the heat elsewhere) Thanks for noticing. It is surprising to me that no one has noticed this (like for the last 10 years or so) until now! But be warned. "d" or "delete" in gdb is different than "d" in perl5db. |
P.S. until I get around to this you can always change this in a startup profile $HOME/.trepanrc such as
|
Thanks for the quick reply! I didn't realize it was specific to this command only, but now that I've tested a few other ones I see that they mostly do work. One other exception I found was "h" which didn't work for "help". I'm not sure to understand the comment about "d" in perl5db though -- does it even have such command? Anyhow, I definitely expected "d" to work as "delete breakpoint", i.e. in the gdb sense. |
Commit 4b6c2ba in github now sets "d" to be "delete". |
I've stumbled upon your blog and as I couldn't agree more with the idea that all debuggers should use gdb commands syntax, I immediately did
cpanm Devel::Trepan
to finally have a Perl debugger I could use without thinking about what I am typing. Unfortunately it doesn't seem to work like I thought it would: while trepan does understand the full gdb commands, it doesn't understand their abbreviations. For example, "d" doesn't work for deleting breakpoints. I don't know if it's intentional or just a bug but I hope it's just the latter and that abbreviations of gdb commands could be made to work too.Thanks in advance!
The text was updated successfully, but these errors were encountered: