From: Jon Turney <jon.turney@dronecode.org.uk>
To: cygwin-developers@cygwin.com
Cc: David McFarland <corngood@gmail.com>
Subject: Re: Fibers and cygtls
Date: Sun, 6 Sep 2020 15:19:33 +0100 [thread overview]
Message-ID: <18df3178-ac42-4d87-d357-459553a8d325@dronecode.org.uk> (raw)
In-Reply-To: <vrit4koda82w.fsf@gmail.com>
On 04/09/2020 16:13, David McFarland via Cygwin-developers wrote:
> For a while now I've been trying to get nix working on Cygwin. It
> compiles fine, but when it's run, it will exit unexpectedly in a way
> that doesn't return an error code to Cygwin, and doesn't break in gdb.
I think this probably means you need to use 'set cygwin-exceptions on'
in gdb. (See [1]).
[1] https://cygwin.com/faq.html#faq.programming.debugging-cygwin
(Yes, gdb could be a lot smarter about what it chooses to ignore)
prev parent reply other threads:[~2020-09-06 14:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-04 15:13 David McFarland
2020-09-04 19:51 ` Corinna Vinschen
2020-09-05 2:46 ` David McFarland
2021-12-20 15:01 ` David McFarland
2021-12-22 15:46 ` David McFarland
2020-09-06 14:19 ` 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=18df3178-ac42-4d87-d357-459553a8d325@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=corngood@gmail.com \
--cc=cygwin-developers@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).