Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: John Baldwin <jhb@freebsd.org>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Fetch all registers before writing the core register notes.
Date: Mon, 16 Mar 2015 14:55:00 -0000	[thread overview]
Message-ID: <1491489.frCxvRgD87@ralph.baldwin.cx> (raw)
In-Reply-To: <5506C7F2.5040605@redhat.com>

On Monday, March 16, 2015 12:09:22 PM Pedro Alves wrote:
> On 03/14/2015 10:02 PM, John Baldwin wrote:
> > Without this, not all registers were present in the core generated by gcore.
> > For example, running 'gcore' on a program without examining the vector 
> > registers (SSE or AVX) would store all the vector registers as zeros because
> > they were not pulled into the regcache.  Running 'info vector' before 'gcore'
> > would store the correct values in the core since it populated the regcache.
> > For Linux processes, a similar operation is achieved somewhat by having the
> > thread iterator callback invoke target_fetch_registers on each thread before
> > its corresponding register notes are dumped.
> > 
> > (I don't plan on including that level of detail in the commit log, just as
> > a way to explain the bug this change fixes.)
> 
> I think it's good to have the detail in the log.  If you felt the need to
> explain it for review, then a future archaeologist looking at git log/blame
> would likely appreciate the same info.

Fair enough, I will include it.

> > gdb/ChangeLog:
> > 
> > 	* fbsd-tdep.c (fbsd_make_corefile_notes): Fetch all target registers
> > 	before writing core register notes.
> 
> Looks fine to me.
> 
> Thanks,
> Pedro Alves
> 


-- 
John Baldwin


      reply	other threads:[~2015-03-16 14:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-14 22:02 John Baldwin
2015-03-16 12:09 ` Pedro Alves
2015-03-16 14:55   ` John Baldwin [this message]

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=1491489.frCxvRgD87@ralph.baldwin.cx \
    --to=jhb@freebsd.org \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.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