You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sadly I currently don't get any output on a Debian system that uses GNU objdump (GNU Binutils for Debian) 2.35.2 and any appimage after /tmp/hotspot-v1.4.1-201-g7906894-x86_64.AppImage (maybe it worked until 211 or so):
stderr does not contain any output - do you have an idea what to check next?
The objdump.indexed_start_internal.log is the requested log of objdump -d -l -C --start-address 0x42ed3 --stop-address 0x43840 --visualize-jumps /tmp/gnucobol-bug-hunting/libcob/.libs/libcob.so.4.2.0 (apart from the filename, but that is a symbolic link in any case).
Another example: objdump.keycompare.log, created by objdump -d -l -C --start-address 0x135f1 --stop-address 0x13abf --visualize-jumps /usr/local/lib/libvbisam.so.4.0.0 > objdump.keycompare.log.
Note that not all disassembly views on this machine are broken, using the same objdump and the same binary, some function are correctly highlighted and split into their parts, while other functions are just one block (so no coloring, highlighting or "navigating" there).
The text was updated successfully, but these errors were encountered:
Sadly I currently don't get any output on a Debian system that uses GNU objdump (GNU Binutils for Debian) 2.35.2 and any appimage after /tmp/hotspot-v1.4.1-201-g7906894-x86_64.AppImage (maybe it worked until 211 or so):
stderr does not contain any output - do you have an idea what to check next?
Originally posted by @GitMensch in #555 (comment)
The objdump.indexed_start_internal.log is the requested log of
objdump -d -l -C --start-address 0x42ed3 --stop-address 0x43840 --visualize-jumps /tmp/gnucobol-bug-hunting/libcob/.libs/libcob.so.4.2.0
(apart from the filename, but that is a symbolic link in any case).Another example: objdump.keycompare.log, created by
objdump -d -l -C --start-address 0x135f1 --stop-address 0x13abf --visualize-jumps /usr/local/lib/libvbisam.so.4.0.0 > objdump.keycompare.log
.Note that not all disassembly views on this machine are broken, using the same objdump and the same binary, some function are correctly highlighted and split into their parts, while other functions are just one block (so no coloring, highlighting or "navigating" there).
The text was updated successfully, but these errors were encountered: