Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Jon TURNEY <jon.turney@dronecode.org.uk>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Retrieve segment registers on Windows amd64
Date: Thu, 26 Feb 2015 09:23:00 -0000	[thread overview]
Message-ID: <20150226092333.GB31815@adacore.com> (raw)
In-Reply-To: <1424435625-3708-1-git-send-email-jon.turney@dronecode.org.uk>

Jon,

> For amd64, CONTEXT_FULL does not contain CONTEXT_SEGMENTS, which seems to be
> needed to retrieve all the segment registers.  Add it explicitly, with
> a little de-cruftification.
> 
> The value of the segment registers isn't terribly useful on amd64, but
> at least this makes the output of 'info registers' correct.
> 
> before:
> 
> (gdb)  i r cs ss ds es fs gs
> cs             0x33     51
> ss             0x2b     43
> ds             0x0      0
> es             0x0      0
> fs             0x0      0
> gs             0x0      0
> 
> after:
> 
> (gdb) i r cs ss ds es fs gs
> cs             0x33     51
> ss             0x2b     43
> ds             0x2b     43
> es             0x2b     43
> fs             0x53     83
> gs             0x2b     43
> 
> gdb/ChangeLog
> 
> 2015-02-19  Jon TURNEY  <jon.turney@dronecode.org.uk>
> 
> 	* windows-nat.c (CONTEXT_DEBUGGER_DR): Add CONTEXT_SEGMENTS.

Thanks for the patch.

The patch looks good to me.
The ChangeLog needs to identify all the changes were made, and in
particular, it needs to mention the fact that CONTEXT_DEBUGGER's
declaration was removed.

Do you have a GDB copyright assignment on file. The patch is small
enough that we can take it as a "tiny patch", but if you have other
patches in the pipeline, then you'll eventually need to fill one out.
Let me know if you'd like to get started on the process, it takes
a few weeks to complete, as I understand it.

-- 
Joel


  reply	other threads:[~2015-02-26  9:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-20 12:59 Jon TURNEY
2015-02-26  9:23 ` Joel Brobecker [this message]
2015-02-26 13:59   ` Jon TURNEY
2015-02-27  8:49     ` Joel Brobecker

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=20150226092333.GB31815@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jon.turney@dronecode.org.uk \
    /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