Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
To debug :
(gdb) target remote:1234
I run the qemu and the gdb on the same machine. I am root and have
set iptables -F. I have also set CONFIG_DEBGUG_INFO.
My problem is that gdb hangs after 'c' . It does not proceed.
When I do Ctrl-C, I observe at the prompt "interrupted while
waiting for the program". I feel I m missing something.
The qemu output is relayed through vnc. But after 'c' in gdb.
I do not see anything in the vncviewer console. I assume that the
kernel is not being executed.
In short, my main problem is debugging with gdb. I am not able to run the kernel using gdb so that I can do a trace analysis at the required breakpoint. I have seen in gdb-tutorials for kernel where they proceed with kernel execution with cont. But that too do not work in my case.