From: Hui Zhu <teawater@gmail.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Sean Soria <sean.soria@gmail.com>,
Michael Snyder <msnyder@vmware.com>,
"gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: Reverse Debugging Headaches
Date: Thu, 14 Jan 2010 05:03:00 -0000 [thread overview]
Message-ID: <daef60381001132102k3e733ecdq609cba87fbea4bf7@mail.gmail.com> (raw)
In-Reply-To: <20100113111126.GA606@host0.dyn.jankratochvil.net>
I don't have myself git. My patch looks like get from git because I
generate patch with quilt. :)
I will try to make mthread support patch check-in in recent days.
For archer, thanks a lot of told me about it. If I have a lot of
off-trunk patch, I will try to use it.
Best regards,
Hui
On Wed, Jan 13, 2010 at 19:11, Jan Kratochvil <jan.kratochvil@redhat.com> wrote:
> Hi Hui,
>
> On Wed, 13 Jan 2010 10:28:47 +0100, Hui Zhu wrote:
>> The prec in cvs-head still doesn't support multi-thread inferior.
>> We just have a series of patches to make prec support multi-thread
>> inferior. You can get the link for it in
>> http://sourceware.org/gdb/wiki/ProcessRecord
>
> ok, sorry I have not tracked it.
>
> Wouldn't you prefer to maintain the off-trunk patches in public Archer GIT?
> http://sourceware.org/gdb/wiki/ArcherBranchManagement
> Or making your own GIT public with some merged branch there.
> You are apparently already developing it in GIT yourself.
> Please ignore me if it was already discussed before.
>
>
> Thanks,
> Jan
>
next prev parent reply other threads:[~2010-01-14 5:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-10 6:03 Sean Soria
2010-01-10 7:38 ` Hui Zhu
2010-01-11 18:54 ` Michael Snyder
2010-01-11 20:44 ` Sean Soria
2010-01-11 20:54 ` Jan Kratochvil
2010-01-11 20:57 ` Sean Soria
2010-01-13 9:29 ` Hui Zhu
2010-01-13 11:12 ` Jan Kratochvil
2010-01-14 5:03 ` Hui Zhu [this message]
2010-01-14 19:00 ` Michael Snyder
2010-01-15 1:43 ` Hui Zhu
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=daef60381001132102k3e733ecdq609cba87fbea4bf7@mail.gmail.com \
--to=teawater@gmail.com \
--cc=gdb@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=msnyder@vmware.com \
--cc=sean.soria@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