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

AppImage fails to analyze: `GLIBC_2.18' not found (required by /tmp/.mount_HotspoRWNh3k/usr/lib/librustc_demangle.so) #250

Closed
lferraro opened this issue Aug 31, 2020 · 9 comments
Labels

Comments

@lferraro
Copy link

lferraro commented Aug 31, 2020

Describe the bug
When loading a perf.log file the application pops an error saying:
The hotspot-perfparser binary exited with code 1 (TCP socket error)

A similar behaviour has been previously reported in #197

To Reproduce
Steps to reproduce the behavior:

  1. create a perf.log of an application with perf
  2. load the file into the hotspot application
  3. see the error :-)

$> ./Hotspot-git.12a5de0-x86_64.AppImage
/tmp/.mount_HotspoRWNh3k/usr/lib/x86_64-linux-gnu/libexec/hotspot-perfparser: /lib64/libc.so.6: version `GLIBC_2.18' not found (required by /tmp/.mount_HotspoRWNh3k/usr/lib/librustc_demangle.so)
"The hotspot-perfparser binary exited with code 1 (TCP socket error)."

Version Info (please complete the following information):

  • Linux Kernel version: CentOS Linux release 7.6.1810 (Core) kernel 3.10.0-957.27.2.el7.x86_64
  • perf version: perf version 3.10.0-957.27.2.el7.x86_64.debug
  • hotspot version: ./Hotspot-git.12a5de0-x86_64.AppImage
@lferraro lferraro added the bug label Aug 31, 2020
@milianw milianw changed the title Perfparser exits with code 1 (TCP Socket error) again AppImage fails to analyze: `GLIBC_2.18' not found (required by /tmp/.mount_HotspoRWNh3k/usr/lib/librustc_demangle.so) Sep 1, 2020
@milianw
Copy link
Member

milianw commented Sep 1, 2020

Ouch, seems like rustc_demangle pulls in a glibc symbol that's incompatible with the CentOS version you have... Not sure when I find the time to investigate this in more detail

@lferraro
Copy link
Author

lferraro commented Sep 1, 2020

Ouch, seems like rustc_demangle pulls in a glibc symbol that's incompatible with the CentOS version you have... Not sure when I find the time to investigate this in more detail

Do you think is there any work around for that?

For example, we use module to load other software and set the proper environment in a terminal. Do you think I can help the AppImage if I set my environment appropriately? What would I need to install?

@milianw
Copy link
Member

milianw commented Sep 2, 2020

the quickest workaround will be to disable the rustc demangling support - I'll create you an appimage for that

but a proper solution will require more time to investigate this problem

milianw added a commit that referenced this issue Sep 2, 2020
This is required for compatibility with CentOS 7, as librustc_demangle
seems to pull in a GLIBC_2.18 symbol that's not available on that
platform.

Relates-To: #250
@milianw
Copy link
Member

milianw commented Sep 2, 2020

@lferraro
Copy link
Author

lferraro commented Sep 3, 2020

Try this one (but note that rustc demangling is disabled): https://github.com/KDAB/hotspot/releases/download/v1.3.0/hotspot-v1.3.0-x86_64-NoRustDemanglingForCentOS7.AppImage

Milian, this version works! Thank you for your work. I'm now able to launch and test performances on this cluster.

Do you think this working configuration can be mantained in future AppImage or could break other host platforms?

@milianw
Copy link
Member

milianw commented Sep 3, 2020

I can submit such an AppImage in the future too - but if anyone wants to do rust demangling on CentOS 7 then a better solution needs to be found. For now, I'll close this as resolved then. Thanks for your confirmation!

@milianw milianw closed this as completed Sep 3, 2020
@GitMensch
Copy link
Contributor

Can you add this special version to the upcoming releases please?

@GitMensch
Copy link
Contributor

Just a note to answer my own question: the delay-load of the plugin with a fallback to "plugin not available" should solve this issue without a special AppImage. Everything we need to do is to wait on the new release (if someone has a pointer where to look at a rough plan: please share).

@milianw
Copy link
Member

milianw commented Apr 13, 2021

I've just uploaded a new appimage to https://github.com/KDAB/hotspot/releases/tag/continuous - but it does not ship with the rust demangler. I'll have to look at building that in my docker env.

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

No branches or pull requests

3 participants