From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: teawater@gmail.com
Cc: gdb-patches@sourceware.org, msnyder@vmware.com
Subject: Re: [RFA/RFC] Prec multi-thread support [1/4] X86 insn support
Date: Wed, 25 Nov 2009 10:44:00 -0000 [thread overview]
Message-ID: <200911251043.nAPAhhsk009017@glazunov.sibelius.xs4all.nl> (raw)
In-Reply-To: <daef60380911250005j6283fcb2sa7cf9e351b8c01cc@mail.gmail.com> (message from Hui Zhu on Wed, 25 Nov 2009 16:05:44 +0800)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 337 bytes --]
> From: Hui Zhu <teawater@gmail.com>
> Date: Wed, 25 Nov 2009 16:05:44 +0800
>
> When I debug i386 multi-thread inferior, it need support int3 and
> rdtsc. So make a patch to support them.
>
> 2009-11-24 Hui Zhu <teawater@gmail.com>
>
> * i386-tdep.c (i386_process_record): Add code for int3 and rdtsc.
Looks reasonable to me.
next prev parent reply other threads:[~2009-11-25 10:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-25 8:06 Hui Zhu
2009-11-25 10:44 ` Mark Kettenis [this message]
2009-11-25 10:57 ` Hui Zhu
2009-11-25 20:04 ` Michael Snyder
2009-11-30 19:58 ` Tom Tromey
2009-12-08 5:53 ` 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=200911251043.nAPAhhsk009017@glazunov.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=gdb-patches@sourceware.org \
--cc=msnyder@vmware.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