From: Jon TURNEY <jon.turney@dronecode.org.uk>
To: cygwin-patches@cygwin.com
Subject: Re: [PATCH] Add minidump write utility
Date: Sun, 09 Feb 2014 12:28:00 -0000 [thread overview]
Message-ID: <52F77482.2080402@dronecode.org.uk> (raw)
In-Reply-To: <20140207174431.GA1640@ednor.casa.cgf.cx>
On 07/02/2014 17:44, Christopher Faylor wrote:
> On Fri, Feb 07, 2014 at 04:36:01PM +0000, Jon TURNEY wrote:
>>
>> This patch adds a 'minidumper' utility, which functions identically to
>> 'dumper' except it writes a Windows minidump, rather than a core file.
>>
>> I'm not sure if this is of use to anyone but me, but since I've had the patch
>> sitting around for a couple of years, here it is...
>>
>> 2014-02-07 Jon TURNEY <jon.turney@dronecode.org.uk>
>>
>> * minidumper.cc: New file.
>> * Makefile.in (CYGWIN_BINS): Add minidumper.
>> * utils.xml (minidumper): New section.
>
> This is awesome. Thanks.
>
> Could you add Red Hat as the copyright holder, like dumper.cc?
>
> You can feel free to check this in and update it as you see fit.
I've checked this in with the following adjustments:
- Fix copyright holder.
- Tweak CreateFile() invocation so we don't fail if the file already exists.
- For compatibility with dumper, terminate the dumped process after dumping
it. Add option -n to disable this behaviour.
next prev parent reply other threads:[~2014-02-09 12:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-07 16:36 Jon TURNEY
2014-02-07 17:14 ` Daniel Colascione
2014-02-09 12:37 ` Jon TURNEY
2014-02-07 17:44 ` Christopher Faylor
2014-02-07 19:18 ` Corinna Vinschen
2014-02-08 15:00 ` Jon TURNEY
2014-02-08 17:18 ` Corinna Vinschen
2014-02-09 12:28 ` Jon TURNEY [this message]
2014-02-08 15:00 ` Jon TURNEY
2014-02-08 20:49 ` Christopher Faylor
2014-02-13 17:40 ` Jon TURNEY
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=52F77482.2080402@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin-patches@cygwin.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).