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: Mon, 11 Jun 2012 21:16:59 +0400 [thread overview]
Message-ID: <4FD6280B.2030105@mvista.com> (raw)
In-Reply-To: <CAHkwNT=DLCm_gfubGV=_SahM5njpA=Z_miA=SEkVeYA9cHMdmA@mail.gmail.com>
Hello.
On 10-06-2012 8:30, Anil Nair wrote:
> On Sun, Jun 10, 2012 at 12:18 AM, Sergei Shtylyov<sshtylyov@mvista.com> wrote:
>> Yeah, KGDB was accepted into kernel exactly for more "poorly fixed
>> patches" to appear. :-)
> I was under the impression that maintainers would never recommend
> kgdb, so never learned to use it.
> If you could guide me and Prasanna on how to use kgdb that would be
> helpful :).
For the starters, Prasanna should ask his KGDB question in the right
mailing list, kgdb-bugreport@lists.sourceforge.net.
> If you were saying it sarcastically, then i failed to
> understand it . :P.
Yes, there was sarcasm. If KGDB was only providing for "poorly fixed
patches", it would have been hardly included in the kernel.
>>> You have to use gdbserver
>> gdbserver is only good for debugging the applications.
> I never knew that..!.
Besides, there's not much difference between remotely debugging
applications via gdbserver and remotely debugging kernel via KGDB.
WBR, Sergei
prev parent reply other threads:[~2012-06-11 17:17 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
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 [this message]
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=4FD6280B.2030105@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.