Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
Hello everyone. I have been using Linux for about half a year (currently RH9) and came across the gdam software for x windows. i had a problem and then noticed that it was listed under the 'bugs' section of their sourceforge site. i wanted to see where the bug was (hoping that the error is really my problem) so i compiled the automake sources and tried to run gdb on the audio-server (first time i've ever tried doing so on a big program i haven't written). gdb acted a little different from normal -- instead of giving me the file.c:line number data like all my simple programs do, i get something like this ---
0xffffe002 in ?? ()
(gdb) break gdas_seekable_mp3_seek
Breakpoint 1 at 0x8064bee
[Switching to Thread 1077632288 (LWP 9014)]
Breakpoint 1, 0x08064bee in gdas_seekable_mp3_seek ()
I would like a way to get some kind of source file / line number data out of gdb rather than the hex codes. Is there any kind of 'approved method' to find this data?