You are not logged in.
Pages: 1
Qt Creator throws a warning:
Could not load shared library symbols for linux-vdso.so.1.
Do you need "set solib-search-path" or "set sysroot"?
And I can't find linux-vdso.so.1 on my system. Where it should be? Do I have to care since debugging working still fine?
Last edited by Procedural (2014-01-18 08:53:06)
Offline
Have you searched the forum?
https://bbs.archlinux.org/viewtopic.php?id=160588
Offline
Have you searched the forum?
https://bbs.archlinux.org/viewtopic.php?id=160588
Of course. That thread have no solution to the problem, "doesn't play nice" is not the technical term for issue.
Also, I've created standard Plane C++ Project, but the warning is still there, so it's not about any particular project.
Last edited by Procedural (2014-01-17 08:09:43)
Offline
I removed Qt Creator and deleted QtProject folder from .config and then I build it freshly, but still no:
http://i.imgur.com/e3OauFf.png
So the problem must be not in Qt Creator.
-- mod edit: read the Forum Etiquette and only post thumbnails http://wiki.archlinux.org/index.php/For … s_and_Code [jwr] --
Offline
Ok, it seems the problem in GDB, not Arch.
Issues is closed for now.
Last edited by Procedural (2014-01-17 10:23:36)
Offline
Please don't use [Closed], it denotes a locked thread.
Not a Scripting issue, moving to NC...
Offline
Please don't use [Closed], it denotes a locked thread.
How do I call it then? It's not solved, but the problem seems a bug or something.
Offline
I'd call it FIXED with a reference to
tl;dr: ld.so is now claiming that the vDSO has been loaded from a file,
which confuses tools like gdb.For anyone following along at home: the vDSO is a small ELF Dynamic
Shared Object that the kernel injects into the address space of every
userspace program it loads; it contains routines used to make syscalls
as efficiently as possible, or even avoid some of them altogether.Rather than being stored in the filesystem like a normal ELF DSO, the
vDSO is embedded in the kernel; in fact, I believe there are normally
multiple possible vDSOs from which the kernel chooses based on things
like the type of CPU in use (depending on, say, what syscall mechanism
is most efficient for it).
Offline
gdb-7.8-1-x86_64.pkg.tar.xz package seems to have that problem.
Temporary solution was to downgrade to package gdb-7.7.1-1-x86_64.pkg.tar.xz
At this point Arch Linux has some rough egdes, but it is to be expected.
Offline
gdb-7.8-1-x86_64.pkg.tar.xz package seems to have that problem.
Temporary solution was to downgrade to package gdb-7.7.1-1-x86_64.pkg.tar.xz
Solution to what? There's no functional impairment here, just a spurious warning that you can completely ignore.
Last edited by falconindy (2014-08-13 17:21:36)
Offline
solved for me executing (message suggested):
$ set solib-search-path
Offline
Pages: 1