public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Keith Christian <keith1christian@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Debugging MariaDB Severe Crash (mysqld daemon dies)
Date: Mon, 30 Jan 2017 14:39:00 -0000	[thread overview]
Message-ID: <CAFWoy7Eerg0NnoA1FOLQfa8w7xas-i4Z2=Dt1jY6Y2i-1edORw@mail.gmail.com> (raw)
In-Reply-To: <CAK0ZC5VsaCFjvsgu+Ct70fU59SF0RmZTZ=CReiFU8-tUkTSvMw@mail.gmail.com>

OwN-3m-All,

If no one from the Cygwin team answers here, perhaps run Cygwin setup
and install the source package from Cygwin and re-compile with all
debugging  turned on (however that's done in MariaDB.)

Only a suggestion, I'm not an expert in the recent changes to Cygwin,
all of which have been very good.

On Sat, Jan 28, 2017 at 11:10 PM, OwN-3m-All <own3mall@gmail.com> wrote:
> I opened a bug here with MariaDB since I don't know what else to do:
>
> https://jira.mariadb.org/browse/MDEV-11931
>
> The link above contains a database dump and the query that causes it
> to crash on Windows running under cygwin.
>
> --
> 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
>

--
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

      reply	other threads:[~2017-01-30 14:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-08 15:30 OwN-3m-All
2017-01-12 12:26 ` OwN-3m-All
2017-01-13 22:16   ` Keith Christian
2017-01-28 23:55     ` OwN-3m-All
2017-01-29  6:10       ` OwN-3m-All
2017-01-30 14:39         ` Keith Christian [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='CAFWoy7Eerg0NnoA1FOLQfa8w7xas-i4Z2=Dt1jY6Y2i-1edORw@mail.gmail.com' \
    --to=keith1christian@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).