From: Warren Young <warren@etr-usa.com>
To: Cygwin-L <cygwin@cygwin.com>
Subject: Re: assert broken?
Date: Sat, 19 Feb 2011 18:32:00 -0000 [thread overview]
Message-ID: <4D600CC8.7040105@etr-usa.com> (raw)
In-Reply-To: <20110217184934.GA25353@home.invalid>
On 2/17/2011 11:49 AM, Stan wrote:
>
> The issue is triggering an assert dumps core.
It's supposed to. The core gets you a backtrace, the exact line of code
which tripped the assertion (you can't always tell just from the text of
the assert()), the state of variables, etc. This is a very good thing;
we wouldn't want it any other way.
--
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
prev parent reply other threads:[~2011-02-19 18:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-17 18:49 Stan
2011-02-17 19:05 ` Larry Hall (Cygwin)
2011-02-19 18:32 ` Warren Young [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=4D600CC8.7040105@etr-usa.com \
--to=warren@etr-usa.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).