From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: PHP 7.0.14 crashing with minimal set of extensions
Date: Tue, 13 Dec 2016 22:23:00 -0000 [thread overview]
Message-ID: <5f9d5b58-ed3b-0270-859a-67df82bf52b7@SystematicSw.ab.ca> (raw)
In-Reply-To: <492357823.20161214003757@yandex.ru>
On 2016-12-13 14:37, Andrey Repin wrote:
> Greetings, Brian Inglis!
>> On 2016-12-13 11:06, Andrey Repin wrote:
>>> Here's strace and stackdump from latest crash with Cygwin
>>> 2.6.1-2
>>> project.rootdir.org/.offload/crash-php-7.14.tar.xz
>>> I've tried full Cygwin rebase to no avail.
>>> Particularly, I've attempted to run Composer test suite.
>> strace? stackdump? attachments? cygcheck -svr?
>> Remember - mailer *MUST* attach as text to get thru!
> 40MB strace? As attach? I'm not sure you're serious.
Ah, you meant:
*http://*project.rootdir.org/.offload/crash-php-7.14.tar.xz
*40MB* strace for someone to look at?
I'm not sure *you're* serious.
Complete info is good but reasonable summary is more workable.
Could perhaps junk the boilerplate strace env and dll setup
chunks and file lookups; or just post stackdump and the last
part of the strace with the symptoms leading up to the crash;
maybe the last part of the PHP log, with an STC to provoke
failure, to get someone's interest piqued to look further?
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
--
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:[~2016-12-13 22:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-13 18:20 Andrey Repin
2016-12-13 19:07 ` Brian Inglis
2016-12-13 21:50 ` Andrey Repin
2016-12-13 22:23 ` Brian Inglis [this message]
2016-12-14 7:35 ` Yaakov Selkowitz
2016-12-14 14:25 ` cyg Simple
2016-12-14 17:20 ` Andrey Repin
2016-12-17 7:30 ` Brian Inglis
2016-12-18 18:51 ` Andrey Repin
2016-12-18 19:47 ` Brian Inglis
2016-12-19 20:21 ` Andrey Repin
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=5f9d5b58-ed3b-0270-859a-67df82bf52b7@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--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).