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.

Sign up for GitHub

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

Jump to bottom

vscode-lldb-linux.vsix 's lldb depends on newer version libstdc++ not exist in old version Linux, recommend using libc++ instead, and build on Old Linux machine #193

Closed
lygstate opened this issue Jul 29, 2019 · 14 comments
Closed

vscode-lldb-linux.vsix 's lldb depends on newer version libstdc++ not exist in old version Linux, recommend using libc++ instead, and build on Old Linux machine #193

lygstate opened this issue Jul 29, 2019 · 14 comments
Labels
fixed Fixed in latest (pre-)release.

Comments

@lygstate
Copy link

lygstate commented Jul 29, 2019 •
edited
Loading

Which OS:Linux localhost 4.4.13-200.nd7.1.x86_64 #1 SMP Fri Jun 24 17:24:12 CST 2016 x86_64 x86_64 x86_64 GNU/Linux
Which VSCode version:
Which extension version:
Which adapter type:
Which LLDB version:

What is the problem and how did you get there:

/usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.21' not found (required by /home/lygstate/.vscode-server/extensions/vadimcn.vscode-lldb-1.2.3/lldb/bin/lldb)
@vadimcn
Copy link
Owner

vadimcn commented Jul 29, 2019

Which distro and version are you running?

@lygstate
Copy link
Author

Very old version Linux, neokylin 5.x

@vadimcn
Copy link
Owner

vadimcn commented Jul 30, 2019

Any idea which version of glibc it uses? I think 2.18 can be supported, maybe even 2.17 (which would enable running on something like CentOS 7 or Ubuntu 14.04). Anything lower than that, - probably not.

@lygstate
Copy link
Author

@vadimcn I have a app running under Ubuntu 14.04 can running in this os.
I suggest glibc lowering down to Ubuntu 14.04 .
We already have official llvm that support running under Ubuntu 14.04.
https://github.com/llvm/llvm-project/releases/download/llvmorg-8.0.1/clang+llvm-8.0.1-x86_64-linux-gnu-ubuntu-14.04.tar.xz

@vadimcn
Copy link
Owner

vadimcn commented Aug 5, 2019

Okay, the minimum glibc version in v1.3.0 is 2.18.
Ubuntu 14.04 is 2.19, so that should work.

@vadimcn vadimcn added the fixed Fixed in latest (pre-)release. label Aug 5, 2019
@awagelight
Copy link

Hi, I use centos 7, the glibc version is 2.17, that cause I cannot use vscode lldb, could we downgrade glibc version to 2.17 so that more people can use this awesome tools.

Thank you very much!

@awagelight
Copy link

awagelight commented Aug 9, 2019 •
edited
Loading

Okay, the minimum glibc version in v1.3.0 is 2.18.
Ubuntu 14.04 is 2.19, so that should work.

@vadimcn The another major publish version of Linux is centos 7, the glibc version in centos 7 is 2.17, could you please think about does there has an easy way to support centos 7?

Thank you very much!

@lygstate
Copy link
Author

I would suggest centos 6, that's old enough:)

@jiangzhe
Copy link

jiangzhe commented Sep 2, 2019

Same issue on CentOS 7.6.
Is there a way to specify the version of glibc to use on startup of the plugin?
see similar issue on cpptools plugin: microsoft/vscode-cpptools#19

@vadimcn
Copy link
Owner

vadimcn commented Sep 3, 2019

Is there a way to specify the version of glibc to use on startup of the plugin?

Yes - you can provide it like this: "lldb.adapterEnv": { "LD_LIBRARY_PATH" : "<custom libc directory>:${env:LD_LIBRARY_PATH}" }

@vadimcn vadimcn mentioned this issue Oct 28, 2019
Closed
@rshevach
Copy link

Hi
I tried the option "lldb.adapterEnv" in settings.json.
The GLIBC_2.18 not found error disappeared.
Now I am getting a general error:
Error: The debugger exited without completing startup handshake.

@vadimcn
Copy link
Owner

vadimcn commented Nov 2, 2019

Please provide verbose log.

@rshevach
Copy link

rshevach commented Nov 4, 2019 via email

@vadimcn
Copy link
Owner

vadimcn commented Dec 11, 2019

@rshevach, sorry, I meant Codelldb log.

@vadimcn vadimcn closed this as completed Feb 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
fixed Fixed in latest (pre-)release.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@lygstate @jiangzhe @vadimcn @awagelight @rshevach