From: "H.J. Lu" <hjl.tools@gmail.com>
To: GDB <gdb-patches@sourceware.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Suresh Siddha <suresh.b.siddha@intel.com>
Subject: Re: PING: PATCH: Enable x86 XML target descriptions
Date: Sun, 28 Feb 2010 20:19:00 -0000 [thread overview]
Message-ID: <6dc9ffc81002281219t389637c7vb1aac459815a4376@mail.gmail.com> (raw)
In-Reply-To: <20100228185116.GB17375@caradoc.them.org>
On Sun, Feb 28, 2010 at 10:51 AM, Daniel Jacobowitz
<dan@codesourcery.com> wrote:
> On Sun, Feb 28, 2010 at 07:40:43AM -0800, H.J. Lu wrote:
>> Are there any comments/suggestions for my latest patch:
>>
>> http://sourceware.org/ml/gdb-patches/2010-02/msg00556.html
>>
>> to enable XML for x86?
>
> I was waiting for you to respond to my question about flag registers.
See:
http://sourceware.org/ml/gdb-patches/2010-02/msg00560.html
http://sourceware.org/ml/gdb-patches/2010-02/msg00564.html
> The discussion trailed off in the discussion about the CS value.
> Is that patch still applicable?
>
Linux x86 kernel maintainer, Peter, has confirmed that checking
CS segment register value is the proper way to use ptrace to
check 32bit process under the current 64bit kernel. There will be
a new ptrace option in 2.6.35 kernel to return the CS.L bit directly.
I will submit a gdb patch to try the new ptrace option first before
failing back checking the CS segment register value.
--
H.J.
next prev parent reply other threads:[~2010-02-28 20:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-28 15:40 H.J. Lu
2010-02-28 18:51 ` Daniel Jacobowitz
2010-02-28 20:19 ` H.J. Lu [this message]
2010-02-28 22:24 ` Daniel Jacobowitz
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=6dc9ffc81002281219t389637c7vb1aac459815a4376@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=hpa@zytor.com \
--cc=suresh.b.siddha@intel.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