From: Csaba Raduly <rcsaba@gmail.com>
To: cygwin list <cygwin@cygwin.com>
Subject: Re: assert creates unusable core dump on current stable Cygwin release
Date: Thu, 10 Oct 2019 20:57:00 -0000 [thread overview]
Message-ID: <CAEhDDbB6WRfph6+TRUgCpPiorTodozfe26GmmqOWjM2vieZn+w@mail.gmail.com> (raw)
In-Reply-To: <1ac90af2-412d-345f-da40-8260ae527096@dronecode.org.uk>
On Thu, Oct 10, 2019 at 9:19 PM Jon Turney wrote:
> (and I guess this patch is not acceptable as-is, as it looks like it
> would break x86)
That was my reaction too.
Csaba
--
You can get very substantial performance improvements
by not doing the right thing. - Scott Meyers, An Effective C++11/14 Sampler
So if you're looking for a completely portable, 100% standards-conformant way
to get the wrong information: this is what you want. - Scott Meyers (C++TDaWYK)
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2019-10-10 20:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-09 7:16 assert does not show output in cygwin test build Biswapriyo Nath
2019-10-09 10:03 ` Takashi Yano
2019-10-09 10:39 ` Pavel Fedin
2019-10-09 10:54 ` Takashi Yano
2019-10-09 11:27 ` Pavel Fedin
2019-10-09 12:39 ` Biswapriyo Nath
2019-10-09 15:31 ` assert creates unusable core dump on current stable Cygwin release Brian Inglis
2019-10-09 17:10 ` Jon Turney
2019-10-09 21:28 ` Brian Inglis
2019-10-10 19:19 ` Jon Turney
2019-10-10 20:57 ` Csaba Raduly [this message]
2019-10-10 22:20 ` Brian Inglis
2019-10-13 16:27 ` Jon Turney
2019-10-13 18:14 ` Brian Inglis
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=CAEhDDbB6WRfph6+TRUgCpPiorTodozfe26GmmqOWjM2vieZn+w@mail.gmail.com \
--to=rcsaba@gmail.com \
--cc=cygwin@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).