From: Jon Turney <jon.turney@dronecode.org.uk>
To: Joshuah Hurst <joshhurst@gmail.com>,
The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: Where do core dumps go in Cygwin?
Date: Sat, 2 Sep 2023 16:28:51 +0100 [thread overview]
Message-ID: <057767cb-ed23-3b4a-134a-bd91579dd785@dronecode.org.uk> (raw)
In-Reply-To: <CAEEMktNV6=DXCik8nfstTN-5b6ufgEH7HjaoypCX4Pa-b6Q6RQ@mail.gmail.com>
On 01/09/2023 21:52, Joshuah Hurst via Cygwin wrote:
> On Fri, Sep 1, 2023 at 3:55 PM Takashi Yano <takashi.yano@nifty.ne.jp> wrote:
>>
>> On Fri, 1 Sep 2023 15:50:32 +0200
>> Joshuah Hurst wrote:
>>> Where do core dumps in Cygwin go? ulimit -c is set to unlimited in
>>> bash, but on SEGV no core dump is created in cwd.
>>>
>>> I need a stack trace for randomly occurring SIGSEGV of an application,
>>> but cannot just instrument every invocation.
>>
>> Read:
>> https://www.cygwin.com/cygwin-ug-net/dumper.html
>>
>> However, unfortunately, cygwin 3.4.8 is missing dumper.exe.
"accidentally missing"
> Why? Will this be fixed for cygwin 3.4.8-2?
This was due to an error in our build scripts (which was not noticed
until after the fact)
It will be present in 3.4.9
prev parent reply other threads:[~2023-09-02 15:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-01 13:50 Joshuah Hurst
2023-09-01 13:55 ` Takashi Yano
2023-09-01 20:52 ` Joshuah Hurst
2023-09-01 21:48 ` Takashi Yano
2023-09-02 15:28 ` Jon Turney [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=057767cb-ed23-3b4a-134a-bd91579dd785@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin@cygwin.com \
--cc=joshhurst@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).