Could not load shared library symbols for linux-vdso.so.1. while debugging

linux gdb glibc
Shady Atef picture Shady Atef · Apr 2, 2014 · Viewed 18.1k times · Source

Not loading VDSO.so is one of the famous bugs you encounter while using gdb and glibc >2.2. I found that was planned to get repaired in gdb 7.5.1, but it wasn't. Okay I found a work-around here Here, but I didn't understand it so how to apply it.

OS: Arch Linux
IDE : QT creator 3.0.82
Compiler : GCC 4.8.2
NB: I am not sure if I am breaking the rules including the link above

Answer

Employed Russian picture Employed Russian · Apr 5, 2014

Not loading VDSO.so is one of the famous bugs you encounter while using gdb and glibc >2.2.

No, it's not. The problem here is simply a useless warning, which you can safely ignore.

I found a work-around here Here, but I didn't understand it so how to apply it.

You didn't find a "workaround". You found a patch to GDB, which disables the warning.

To apply it, use the patch command, and then build your own GDB. But it is much simpler to just ignore the warning in the first place.

Related questions

How do I analyze a program's core dump file with GDB when it has command-line parameters?

My program operates like this: exe -p param1 -i param2 -o param3 It crashed and generated a core dump file, core.pid. I want to analyze the core dump file by gdb ./exe -p param1 -i param2 -o param3 core.…

Read More
How do I pass a command line argument while starting up GDB in Linux?

I have to debug a program that has errors in it as part of my assignment. However, I must first pass command line arguments in order to solve this problem. I do: gdb -tui InsertionSortWithErrors which works, but after that …

Read More
Can I use GDB to debug a running process?

Under linux, can I use GDB to debug a process that is currently running?

Read More