From: Michael Snyder <msnyder@specifix.com>
To: Tea <teawater@gmail.com>
Cc: drow@false.org, Thiago Jung Bauermann <bauerman@br.ibm.com>,
gdb-patches@sourceware.org
Subject: Re: GDB record patch 0.1.3.1 for GDB-6.8 release
Date: Tue, 20 May 2008 18:51:00 -0000 [thread overview]
Message-ID: <1211305227.3601.62.camel@localhost.localdomain> (raw)
In-Reply-To: <daef60380805192055x257c4ed7s64a3a258fa71e51e@mail.gmail.com>
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
next prev parent reply other threads:[~2008-05-20 17:40 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-23 8:55 Tea
2008-05-20 4:33 ` Thiago Jung Bauermann
2008-05-20 6:38 ` Daniel Jacobowitz
2008-05-20 15:32 ` Tea
2008-05-20 18:51 ` Michael Snyder [this message]
2008-05-21 17:26 ` Tea
2008-05-20 15:33 ` Tea
2008-05-21 17:14 ` Tea
2008-05-21 22:01 ` Michael Snyder
2008-05-21 22:16 ` Thiago Jung Bauermann
2008-05-21 22:40 ` Daniel Jacobowitz
2008-05-22 15:08 ` Thiago Jung Bauermann
2008-05-23 2:54 ` Tea
2008-05-23 4:33 ` Michael Snyder
2008-05-23 14:33 ` Tea
2008-05-23 16:46 ` Michael Snyder
2008-05-23 18:16 ` Tea
2008-05-23 3:52 ` Pedro Alves
2008-05-23 14:31 ` Tea
2008-05-23 21:10 ` Pedro Alves
2008-06-08 6:53 ` teawater
2008-06-09 0:52 ` Pedro Alves
2008-06-09 3:00 ` Daniel Jacobowitz
2008-06-09 13:58 ` Thiago Jung Bauermann
2008-06-10 2:04 ` Michael Snyder
2008-06-09 22:56 ` Michael Snyder
2008-06-11 11:59 ` teawater
2008-06-11 20:03 ` Michael Snyder
2008-06-12 18:10 ` teawater
2008-06-13 6:08 ` Michael Snyder
2008-06-14 6:24 ` teawater
2008-06-14 10:31 ` Michael Snyder
2008-06-15 3:27 ` teawater
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1211305227.3601.62.camel@localhost.localdomain \
--to=msnyder@specifix.com \
--cc=bauerman@br.ibm.com \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=teawater@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox