[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BANLkTimHwt=q4K9uMNX4kR6Q8LJhHHSysw@mail.gmail.com>
Date: Fri, 8 Apr 2011 13:36:11 +0800
From: Hui Zhu <teawater@...il.com>
To: Peter Zijlstra <peterz@...radead.org>
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, Apr 6, 2011 at 16:19, Peter Zijlstra <peterz@...radead.org> wrote:
> 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?
>
Thanks Peter. I think it is very good.
Which part do you think kgtp can share with kgdb?
Thanks,
Hui
--
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