From: Sean Chen <sean.chen1234@gmail.com>
To: Hui Zhu <teawater@gmail.com>
Cc: Jie Zhang <jie.zhang@analog.com>, gdb@sourceware.org
Subject: Re: Ramp up documents
Date: Tue, 03 Nov 2009 09:08:00 -0000 [thread overview]
Message-ID: <5e81cb500911030108v6155f073p32bbbd80797c0a24@mail.gmail.com> (raw)
In-Reply-To: <daef60380911022230n5808deeci958431f99bd8cc8e@mail.gmail.com>
On Tue, Nov 3, 2009 at 2:30 PM, Hui Zhu <teawater@gmail.com> wrote:
> Thanks for remind me.
>
> I am working on MIPS porting. Nobody is working on ARM. I will post
> it to wiki.
>
> BTW, I think ask the question in maillist and irc is not a bad idea.
>
> Thanks,
> Hui
>
> On Mon, Nov 2, 2009 at 16:12, Sean Chen <sean.chen1234@gmail.com> wrote:
>> Hi Jie,
>>
>> Thanks. It’s helpful.
>>
>> Do we have more detailed information? For example, reversible
>> debugging TODO list shows that MIPS and ARM port is ongoing, but it
>> doesn’t contain the information on the developers and status. Could
>> you throw me a hint on how to get this kind of information? Thanks.
>>
>> Best Regards,
>> Sean Chen
>>
>
Hi Hui,
That’s great. Thanks.
This technique is really excellent and I am very interested in it. I
will first search the mailing list to build a concept and see whether
I can do something on ARM.
Currently, I have got the entrance to GDB wiki, the project on
SourceForge and a slide by you. I appreciate your help if you have
other useful documents at hand.
Best Regards,
Sean Chen
next prev parent reply other threads:[~2009-11-03 9:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-02 5:04 Sean Chen
2009-11-02 6:03 ` Jie Zhang
2009-11-02 8:12 ` Sean Chen
2009-11-02 8:46 ` Jie Zhang
2009-11-02 9:03 ` Sean Chen
2009-11-03 6:30 ` Hui Zhu
2009-11-03 9:08 ` Sean Chen [this message]
2009-11-02 15:17 ` Tom Tromey
2009-11-03 9:12 ` Sean Chen
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=5e81cb500911030108v6155f073p32bbbd80797c0a24@mail.gmail.com \
--to=sean.chen1234@gmail.com \
--cc=gdb@sourceware.org \
--cc=jie.zhang@analog.com \
--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