From: Sergei Shtylyov <sshtylyov@mvista.com>
To: Anil Nair <anilcoll90@gmail.com>
Cc: prasannatsmkumar <prasannatsmkumar@gmail.com>,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: Break point not hit while debugging linux kernel with kgdb
Date: Sat, 09 Jun 2012 22:48:31 +0400 [thread overview]
Message-ID: <4FD39A7F.9020106@mvista.com> (raw)
In-Reply-To: <CAHkwNT=3dGTZTDWi+r7m=K=Pqgv6Txi-xKcpN_pNUJ_WbUaD4w@mail.gmail.com>
Hello.
On 06/09/2012 10:23 PM, Anil Nair wrote:
>> Hi,
>> I tried to debug the linux kernel with kgdb (over serial port).
> The Maintainers would never recommend the use of a debugger, it
> results in poorly fixed patches.
Yeah, KGDB was accepted into kernel exactly for more "poorly fixed patches"
to appear. :-)
>> I have
>> configured the host and target machines and I am able to connect, step
>> in the kernel code. In gdb I gave "break usb_register_dev" and "break
>> usb_deregister_dev" and continued the execution (continue in gdb).
>> Once the desktop is up, I connected a USB device (first tried with USB
>> keyboard). Break point was not hit. I tried some more functions and
>> break points are never hit. What should I do for it? Am I missing
>> something?
> You have to use gdbserver
gdbserver is only good for debugging the applications.
WBR, Sergei
next prev parent reply other threads:[~2012-06-09 18:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-28 10:16 Break point not hit while debugging linux kernel with kgdb prasannatsmkumar
2012-06-09 18:23 ` Anil Nair
2012-06-09 18:48 ` Sergei Shtylyov [this message]
2012-06-10 4:30 ` Anil Nair
2012-06-10 4:50 ` prasannatsmkumar
2012-06-11 3:37 ` Anil Nair
2012-06-11 6:10 ` prasannatsmkumar
2012-06-11 17:16 ` Sergei Shtylyov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4FD39A7F.9020106@mvista.com \
--to=sshtylyov@mvista.com \
--cc=anilcoll90@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=prasannatsmkumar@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox