Quote:
Originally Posted by eschwartz
Kevin, any good reason not to simply start sigil via "gdb sigil"?
|
Because "sigil" isn't a debuggable binary file. It's a bash script. It sets the necessary environment before executing the sigil-real binary. And calling "gdb sigil-real" will likely fail without the environment being set.
Quote:
|
Modifying system files as root to hardcode one-time uses of e.g. gdb is not the recommended way to go about doing things...
|
Maybe not. but necessity is the mother of invention.
Still, you have a point. One could always cd to /usr/local/share/sigil and then attach gdb to the sigil-real binary by doing something like:
Code:
LD_LIBRARY_PATH=/usr/local/share/sigil SIGIL_PLUGIN_LAUNCHERS=/usr/local/share/sigil/plugin_launchers gdb ./sigil-real
Then:
But if
I'm the one going to be doing lots of Sigil debugging ... I'm going to temporarily edit that launch script and put it back when I'm done (or create a new gdb launch script in my home directory if sudo is an issue)