From: Pedro Alves <palves@redhat.com>
To: Markus Metzger <markus.t.metzger@intel.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v2 2/3] gcore, target: allow target to prepare/cleanup for/after core file generation
Date: Tue, 24 Jun 2014 13:11:00 -0000 [thread overview]
Message-ID: <53A978E6.8010901@redhat.com> (raw)
In-Reply-To: <1403599872-25299-2-git-send-email-markus.t.metzger@intel.com>
On 06/24/2014 09:51 AM, Markus Metzger wrote:
> Add new target functions to_prepare_to_generate_core and
> to_done_generating_core that are called before and after generating a core
> file, respectively.
>
> This allows targets to prepare for core file generation and to clean up
> afterwards.
>
> 2014-06-24 Markus Metzger <markus.t.metzger@intel.com>
>
> * target.h (target_ops) <to_prepare_to_generate_core>
> <to_done_generating_core>: New.
> (target_prepare_to_generate_core, target_done_generating_core): New.
> * target.c (target_prepare_to_generate_core)
> (target_done_generating_core): New.
> * target-delegates.c: Regenerate.
> * gcore.c: (write_gcore_file): Rename to ...
> (write_gcore_file_1): ...this.
> (write_gcore_file): Call target_prepare_to_generate_core
> and target_done_generating_core.
OK.
Thanks,
--
Pedro Alves
next prev parent reply other threads:[~2014-06-24 13:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-24 8:51 [PATCH v2 1/3] make_corefile_notes: have caller free returned memory Markus Metzger
2014-06-24 8:51 ` [PATCH v2 2/3] gcore, target: allow target to prepare/cleanup for/after core file generation Markus Metzger
2014-06-24 13:11 ` Pedro Alves [this message]
2014-06-24 8:52 ` [PATCH v2 3/3] btrace: pretend we're not replaying when generating a core file Markus Metzger
2014-06-24 13:19 ` Pedro Alves
2014-06-24 12:58 ` [PATCH v2 1/3] make_corefile_notes: have caller free returned memory Pedro Alves
2014-06-24 13:44 ` Tom Tromey
2014-06-24 14:18 ` Metzger, Markus T
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=53A978E6.8010901@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=markus.t.metzger@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