[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110421024648.GA24898@home.goodmis.org>
Date: Wed, 20 Apr 2011 22:46:49 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Hui Zhu <teawater@...il.com>
Cc: Dongdong Deng <libfetion@...il.com>,
Jason Wessel <jason.wessel@...driver.com>,
Peter Zijlstra <peterz@...radead.org>,
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>
Subject: Re: KGTP (Linux Kernel debugger and tracer) 20110405 release
On Fri, Apr 08, 2011 at 04:25:28PM +0800, Hui Zhu wrote:
> After a discussion with Dongdong, I think I have different idea with that.
>
> 1. I don't want change the current interface of kgtp. Because a proc
> interface is very simple and stable interface.
> And with proc, kgtp can very easy connect with GDB without Kernel
Can you use the debugfs interface instead of proc. Proc is too
overloaded as is, and debugfs seems to be a perfect match in this case.
-- Steve
> help. Please see
> https://code.google.com/p/kgtp/wiki/HOWTO#Make_GDB_connect_to_gtp and
> https://code.google.com/p/kgtp/wiki/HOWTO#Offline_debug
>
> 2. I don't want remove the kprobe. Because what I want kgtp is to be
> a Linux Kernel tracepoint interface with gdb. I will add other
> tracepoint like TRACE_EVENT.
> And move it to gdb breakpoint is too far away from it. And it is too
> much depend on kgdb.
>
> Of course, I am very happy to share the GDB rsp tracepoint parse code
> with kgdb to make it support gdb tracepoint.
> Trust me, My code is more clear than the doc of GDB. :)
>
--
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