From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin@cygwin.com
Cc: Joshuah Hurst <joshhurst@gmail.com>
Subject: Re: Where do core dumps go in Cygwin?
Date: Fri, 1 Sep 2023 22:55:39 +0900 [thread overview]
Message-ID: <20230901225539.4a9e06a30d0f5b7f09e4641c@nifty.ne.jp> (raw)
In-Reply-To: <CAEEMktP7o=7OA1YHy7opgeXdWZvN-Xi1MAygRUpVyVzcqZcFdA@mail.gmail.com>
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.
Please use latest cygwin 3.5.0 (Test) or cygwin 3.4.7 so far.
--
Takashi Yano <takashi.yano@nifty.ne.jp>
next prev parent reply other threads:[~2023-09-01 13:55 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 [this message]
2023-09-01 20:52 ` Joshuah Hurst
2023-09-01 21:48 ` Takashi Yano
2023-09-02 15:28 ` 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=20230901225539.4a9e06a30d0f5b7f09e4641c@nifty.ne.jp \
--to=takashi.yano@nifty.ne.jp \
--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).