[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <4FD6280B.2030105@mvista.com>
Date: Mon, 11 Jun 2012 21:16:59 +0400
From: Sergei Shtylyov <sshtylyov@...sta.com>
To: Anil Nair <anilcoll90@...il.com>
CC: prasannatsmkumar <prasannatsmkumar@...il.com>,
linux-kernel@...r.kernel.org, linux-usb@...r.kernel.org
Subject: Re: Break point not hit while debugging linux kernel with kgdb
Hello.
On 10-06-2012 8:30, Anil Nair wrote:
> On Sun, Jun 10, 2012 at 12:18 AM, Sergei Shtylyov<sshtylyov@...sta.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@...ts.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists