GDB warning: bootable partition not found on added DS system with file system with symbol file system at 0x7ffff7ffd000

abijith bufferOverFlow $ gdb a.out GNU gdb (GDB) 7.6 Copyright (C) 2013 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-unknown-linux-gnu". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... Reading symbols from /home/abijith/Project/Security/bufferOverFlow/a.out...done (gdb) r Starting program: /home/abijith/Projec2qt/Security/bufferOverFlow/a.out warning: no loadable sections found in added symbol-file system-supplied SO at 0x7ffff7ffd000 

I wrote a simple program that prints a string and returns. I was able to execute it directly by typing "./a.out". But when I run it in gdb, the error mentioned above occurs. I tried to compile the code using the "-g" flag and not using it. Both times he gave the same result. Can someone help me with this problem?

+8
gcc linux gdb
source share
2 answers

This is a message

 warning: no loadable sections found in added symbol-file system-supplied 

SO at 0x7ffff7ffd000

- a warning that does not prevent GCC a.out from starting; at least it should not be.

They say that there is a dynamically loaded object that uses a.out , which does not contain characters. Nothing about a.out itself.

You can try building a.out as a static executable; eg:

 gcc -static ac 

Obviously add any other compiler arguments.

As a static executable, you will not receive this warning from GCC. These characters may still be missing, but this should not affect program execution.

+3
source share

This seems to be a bug in glibc or gdb (depending on where you want to put the blame). This is apparently harmless - gdb will work fine.

This is caused by some magic that the Linux kernel executes in executable files. See the Debian 738702 Error Report and the original gdb 13097 Error Report for more information.

There is a fix that fixed this Debian, so the problem no longer occurs with GDB 7.7.1 on Debian.

+2
source share

All Articles