extend appimage debugging notes #459
Conversation
GitMensch
force-pushed
the
patch-1
branch
3 times, most recently
from
6758159 to
f6419fe
Compare
|
|
||
| ```bash | ||
| $ ./hotspot-v1.4.0-43-g02fd82c-x86_64.AppImage --appimage-extract | ||
| $ PATH=./squashfs-root/usr/bin:$PATH LD_LIBRARY_PATH=./squashfs-root/usr/lib64:/usr/local/lib64:/usr/lib64:./squashfs-root/usr/lib:$LD_LIBRARY_PATH gdb -q --exec=hotspot --symbols hotspot-debuginfo-v1.4.0-43-g02fd82c/usr/bin/hotspot -ex run |
There was a problem hiding this comment.
maybe we should add some kind of --appimage-debug gdb or similar to our AppRun which would prepend the debugger before starting hotspot?
or maybe better: extract the code that sets up the env from the AppRun, such that we can do:
source appimage.env
gdb -q --exec=hotspot --symbols hotspot-debuginfo-v1.4.0-43-g02fd82c/usr/bin/hotspot -ex run
directly?
There was a problem hiding this comment.
appimage.env would be marvelous! Even better would be if appimage can be executed, too: /path/to/appimage.env hotspot (or, using gdb that way).
--appimage-debug Name-Of-Debugger-Here [additional debugger arguments] [-- additional arguments passed to hotspot] would be nice, too; allowing things like /hotspot-v1.4.0-43-g02fd82c-x86_64.AppImage --appimage-debug /opt/path/to/newer/gdb/bin/gdb -x additional_printers.gdb --args -- some.perf.data
There was a problem hiding this comment.
Should we create one (or two) issue(s) for those good ideas of yours?
|
Thanks for the review - no further changes planned. |
No description provided.