LinuxGeneral discussion of programming the various flavors of Linux operating systems.
Welcome to the p2p.wrox.com Forums.
You are currently viewing the Linux section of the Wrox p2p Programmer to Programmer discussion community. This is a community of more than 40,000 computer programmers including Wrox book authors and readers. As a guest, you can read any forum posting. By joining our free Wrox p2p community you can post your own programming questions and respond to other programmers’ questions. Registered users also don't have to see the ads that are displayed to guests. Registration is fast, simple and absolutely free so please, join today!
Join today and post to win prizes! Post more to increase your chances of being Wrox’s top poster of the month.
At first. I want to say that I'm sorry because of my english that it is not very good.
I'm trying to debug a driver that I'm developing in a computer with kgdb in the kernel. I want to debug the driver from another computer using gdb. My problem is when after I connect gdb with kgdb:
1- The kgdb computer boots and wait to the other computer connection.
2- In the gdb computer I connect with kgdb computer.
3- In the gbd sotfware I write 'c' to say to kgdb computer that continue booting the kernel.
4- The kgbd computer finish the boot. But in gdb software I don't see the prompt.
I would like to know what is the problem, or if it's the natural behaviour of gdb.
Thank you.
Last edited by cledesma : August 2nd, 2009 at 08:25 AM.
Reason: delete
Kgdb: using kgdboc (Kgdb over console)
Linear Mode
