SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
When launching gdb on an application I am greeted with the following error:
&"warning: GDB: Failed to set controlling terminal: Inappropriate ioctl for device\n"
Could not load shared library symbols for linux-gate.so.1.
Do you need "set solib-search-path" or "set sysroot"?
Some googling of this provided a whole myriad of garbage, from patches to finger pointing, and other sorts of hand waiving.
Frequently people say that this is a harmless warning and can be ignored. I am thinking that is not the case.
I am debugging a 32bit application. SlackVer is x64.
GDB gets the shared kernel object : linux-vdso.so.1 which resides at 0x00007fffc7dde000
my application gets: linux-gate.so.1 which resides at 0xffffe000
At any rate, gdb is not working right at all. I can set break points, step through, step over etc. That's all fine an dandy, however it fails to give me values if I add an expression evaluation. I can set a break point before a variable is set, at it, then immediately after. GDB stops at all the points but does not have a value for me.
This makes debugging next to impossible with gdb.
If anyone had this issue and has since resolved it your input would be greatly appreciated.
[Edit]: For what its worth I am debugging a multi thread program which is interfacing with other applications.