libtool aware gdb wrapper and mergetool
Just want to mention some small and rough tools I've written recently to easy my daily hacker's life:
-
gdb-wrapper: gdb doesn't know what to do with libtool generated wrapper scripts. Quite strange that over the years nobody felt annoyed enough to tell gdb about those wrapper scripts. At least I was sufficiently annoyed to write this tiny wrapper script, which redirects gdb to the debuggable .libs/lt-program binary when gdb is invoked on some libtool generated wrapper script. It also takes care about generating that binary if it shouldn't exist yet. Be warned: The script really just does the bare minimum.
-
mergetool: Yes many of git's commands support some interactive mode. Expect maybe for 'git-rebase --interactive' they all have poor usability. So here is my graphical version of 'git-add -i'. This tool allows picking patch hunks from other branches. You also can edit the hunks if you figure out that one of them should be split into separate commits.
Both tools are quite rough, but maybe some of you find them useful.
Update: Seems that "libtool --mode=execute cmdline..." works similar to my wrapper script. Thanks for pointing me on this.
Use Nemiver !
Benoît: Not an option when various reason require you build and test your code in a chroot like environment.
You'll find that more recent versions of git don't support git-foo style commands. You have to use the git foo equivalents.
For your GDB problem, you can use
$libtool gdb myexecutable
It's written in the libtool doc:
http://www.gnu.org/software/libtool/m...
Damien: Oh! Thanks alot.
Brad: Oh! No! So I'd have to activate those completly broken bash-completion scripts to get shell completion for git commands!? This is horrible!
I'd be happy if you'd merge, mergetool into giggle :)
Mathias Hasselmann: At least zsh complete the commands (git reb<TAB>).
How does mergetool compare to git-gui^Wgit gui?
Ka-Hing: mergetool is much more primitive since it does just one single task: Merging changes from some other branch. On the other hand is uses some reasonable UI toolkit. Tcl/Tk doesn't even match the minimum requirement for a useful UI toolkit: It is not even capable of rendering readable text.
I seriously wonder why people waste time on obsolete stuff like Tcl/Tk: http://taschenorakel.de/pictures/scre...
I wonder why so much stuff is done in tk either. git gui, gitk, isn't make menuconfig also tk?
As to git rebase --interactive being sane, I am going to disagree here. I could never wrap my head around enough to use either git add -i or git rebase -i.