Skip to content
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

Disassembly view: Disassembly broken after 201 #561

Closed
GitMensch opened this issue Nov 12, 2023 · 1 comment
Closed

Disassembly view: Disassembly broken after 201 #561

GitMensch opened this issue Nov 12, 2023 · 1 comment

Comments

@GitMensch
Copy link
Contributor

GitMensch commented Nov 12, 2023

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):

grafik
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).

@GitMensch
Copy link
Contributor Author

fixed by #566

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant