From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17926 invoked by alias); 20 May 2008 17:40:46 -0000 Received: (qmail 17918 invoked by uid 22791); 20 May 2008 17:40:46 -0000 X-Spam-Check-By: sourceware.org Received: from bluesmobile.specifix.com (HELO bluesmobile.specifix.com) (216.129.118.140) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 20 May 2008 17:40:29 +0000 Received: from [127.0.0.1] (bluesmobile.specifix.com [216.129.118.140]) by bluesmobile.specifix.com (Postfix) with ESMTP id 5B3A33C56E; Tue, 20 May 2008 10:40:27 -0700 (PDT) Subject: Re: GDB record patch 0.1.3.1 for GDB-6.8 release From: Michael Snyder To: Tea Cc: drow@false.org, Thiago Jung Bauermann , gdb-patches@sourceware.org In-Reply-To: References: <1211231955.32587.23.camel@localhost.localdomain> <20080519212903.GA869@caradoc.them.org> Content-Type: text/plain Date: Tue, 20 May 2008 18:51:00 -0000 Message-Id: <1211305227.3601.62.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.10.3 (2.10.3-7.fc7) Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2008-05/txt/msg00604.txt.bz2 On Tue, 2008-05-20 at 11:55 +0800, Tea wrote: > Agree with Daniel. > I think current way is better than include Linux kernel header files. > > To compile GDB with Linux KERNEL? I think it will make compile GDB not > very easy. If the Linux Kernel change. The user need re-compile the > GDB? > Or add Linux Kernel files to GDB directory? It looks not very > professional. And maybe will cause some copyright problem. > > And this types size will not change very continually. The GLIBC use it > too. The kernel more like add new types than change the old types. There is another possibility. You might build something resembling gdbserver, and put the record/playback functionality in there. Have gdb talk to it by the remote serial protocol (over a socket, of course). There is an old branch in the cvs repository where we have stashed away a version of gdb that has some extra "reverse" syntax in the remote protocol. This would have the advantage of a clear separation layer, so that gdb would not have to be "poluted" by foreign header files with different copyrights and licensing, plus keeping a big chunk of complex code separate from gdb itself. Plus, you could now reverse-debug from one host to another, even across different architectures. Just an idea... Michael