[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1302077959.2225.1378.camel@twins>
Date: Wed, 06 Apr 2011 10:19:19 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Hui Zhu <teawater@...il.com>
Cc: linux-kernel@...r.kernel.org,
Marc Khouzam <marc.khouzam@...csson.com>,
Thiago Jung Bauermann <thiago.bauermann@...il.com>,
Steven <mqyoung@...il.com>, colyli@...il.com,
Christoph Hellwig <hch@...radead.org>,
Jason Wessel <jason.wessel@...driver.com>
Subject: Re: KGTP (Linux Kernel debugger and tracer) 20110405 release
On Wed, 2011-04-06 at 13:54 +0800, Hui Zhu wrote:
> This is a good question.
>
> The KGTP is completely different with KGDB. It will not supply simple
> gdbrsp debug interface to user. It just supply interface between the
> kernel tracepoint(Now, just support kprobe, will add others later) and
> GDB tracepoint function.
>
> So user can debug and trace Linux kernel with GDB without stop the
> Linux Kernel (So the GDB can running on this Kernel). It is a trace
> tools and debug tools.
But this isn't really an answer either. Could you extend the existing
KGDB infrastructure to provide these features and thereby re-use
existing infrastructure to reduce your patch size and code duplication?
Jason (the KGDB maintainer) certainly thought there was much possibility
there when I spoke to him yesterday.
Think of it this way, wouldn't it be much better if there was one tool
that could provide the combined feature set of KGDB and KGTP?
--
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