ProgrammingThis forum is for all programming questions.
The question does not have to be directly related to Linux and any language is fair game.
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.
I always write source code and use
gcc -g somefile.c
to creat program which can debug by gdb.
And now, I am reading a little bigger program's source code.
I made some change and want to debug it.
I only can
to run it and see the result.
I want to kown, how to debug it with gdb on this condition?
I don't konw a lot about configure and make, if there is some books to explain thes ?
if you just run ./configure and then make you will get the
binaries where ever the programer configured make to put them.
of course you could ask the program maintainers how to debug it
the GNU c programming tutorial has notes on using make
But if you are in a professional environment (i.e. a job) it's best to keep it simple.
A combination of vi and make will be on virtually every system. As you become
skilled you build up tricks, scripts templates etc. and it becomes a lot more
efficient to work in this way.
If it wasn't true vi and make would have died years ago!