Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: hjl.tools@gmail.com
Cc: gdb-patches@sourceware.org
Subject: Re: PATCH: Check section size for valid core sections
Date: Sun, 07 Feb 2010 21:15:00 -0000	[thread overview]
Message-ID: <201002072115.o17LFFnT030072@glazunov.sibelius.xs4all.nl> (raw)
In-Reply-To: <20100207174213.GA10424@lucon.org> (hongjiu.lu@intel.com)

> Date: Sun, 7 Feb 2010 09:42:13 -0800
> From: "H.J. Lu" <hongjiu.lu@intel.com>
> 
> I added a new core section, .reg-xstate, to support x86 XSAVE extended
> state.  We can read it on any machine. But we can only write it on
> machines with x86 XSAVE extended state. I have
> 
> /* Supported register note sections.  */
> static struct core_regset_section amd64_linux_regset_sections[] =
> {
>   { ".reg", 144, "general-purpose" },
>   { ".reg2", 512, "floating-point" },
>   { ".reg-xstate", 0, "XSAVE extended state" },
>   { NULL, 0 }
> };
> 
> I update its size with
> 
>  /* Update the XSAVE extended state size on Linux/x86 host.  Need it
>     for "gcore".  */
>   i386_xstate_init ();
>   amd64_linux_regset_sections[2].size = i386_xstate.size;
> 
> If the machine suppors XSAVE, size will be non-zero. We can still
> read the core section since size is only used for gcore. OK to install?

Sorry, but this makes no sense to me.

> 2010-02-07  H.J. Lu  <hongjiu.lu@intel.com>
>  
> 	* linux-nat.c (linux_nat_do_thread_registers): Check section
> 	size instead of section name for valid core sections.
> 
> diff --git a/gdb/linux-nat.c b/gdb/linux-nat.c
> index 7fc9584..44a3288 100644
> --- a/gdb/linux-nat.c
> +++ b/gdb/linux-nat.c
> @@ -4112,9 +4112,12 @@ linux_nat_do_thread_registers (bfd *obfd, ptid_t ptid,
>    /* The loop below uses the new struct core_regset_section, which stores
>       the supported section names and sizes for the core file.  Note that
>       note PRSTATUS needs to be treated specially.  But the other notes are
> -     structurally the same, so they can benefit from the new struct.  */
> +     structurally the same, so they can benefit from the new struct.  We
> +     check section size instead of section name for valid core sections
> +     since we can read x86 XSAVE extended state core section, but we can
> +     write it only if x86 XSAVE extended state is available natively.  */
>    if (core_regset_p && sect_list != NULL)
> -    while (sect_list->sect_name != NULL)
> +    while (sect_list->size != 0)
>        {
>  	/* .reg was already handled above.  */
>  	if (strcmp (sect_list->sect_name, ".reg") == 0)
> 


  reply	other threads:[~2010-02-07 21:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-07 17:44 H.J. Lu
2010-02-07 21:15 ` Mark Kettenis [this message]
2010-02-07 21:25   ` H.J. Lu

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=201002072115.o17LFFnT030072@glazunov.sibelius.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --cc=gdb-patches@sourceware.org \
    --cc=hjl.tools@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