From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: crash on latest cygwin snapshot
Date: Thu, 02 Aug 2012 15:57:00 -0000 [thread overview]
Message-ID: <501A946A.2030102@cornell.edu> (raw)
In-Reply-To: <20120801125834.GH17949@calimero.vinschen.de>
On 8/1/2012 8:58 AM, Corinna Vinschen wrote:
> On Aug 1 08:46, Ken Brown wrote:
>> On 8/1/2012 8:29 AM, Corinna Vinschen wrote:
>>> On Aug 1 12:34, marco atzeri wrote:
>>>> On 8/1/2012 11:43 AM, Corinna Vinschen wrote:
>>>>> Hi Marco, Hi Ken,
>>>>>
>>>>> On Jul 2 16:43, marco atzeri wrote:
>>>>>> On 6/27/2012 3:46 AM, Christopher Faylor wrote:
>>>>>>>
>>>>>>> Sorry, Marco. Nevermind. I duplicated this. No need to upload anything.
>>>>>>> I'm still working on it.
>>>>>>>
>>>>>>> cgf
>>>>>>>
>>>>>>
>>>>>> it seems solved on 20120702 snapshots
>>>>>
>>>>> can you please test your crashing scenarios with the latest developer
>>>>> snapshot from today? After some private discussion, cgf and I have a
>>>>> hunch that the underlying problem was the problem I fixed yesterday, and
>>>>> cgf's changes to Makefile.in on 2012-07-01 made just enough changes in
>>>>> code optimization so that your problem wasn't visible anymore.
>>>>>
>>>>> I reverted cgf's changes to Makefile.in and generated the today's
>>>>> snapshot specificially to test our hypothesis. Please give it a try.
>>>>>
>>>>>
>>>>> Thanks,
>>>>> Corinna
>>>>>
>>>>
>>>> $ uname -a
>>>> CYGWIN_NT-6.1-WOW64 MARCOATZERI 1.7.17s(0.262/5/3) 20120801 11:02:01
>>>> i686 Cygwin
>>>>
>>>> is not crashing.
>>>
>>> Thanks for the quick feedback! Now let's see what Ken reports...
>>
>> I never had a reliable way of reproducing the crash (see
>> http://cygwin.com/ml/cygwin/2012-06/msg00464.html). It happened
>> seemingly at random, and very sporadically. But I have the snapshot
>> installed and will exercise it as much as I can.
>
> Thanks!
The good news: I haven't seen a repeat of that old crash so far.
Unfortunately, I'm finding that emacs is unstable: The emacs window
(running under X) simply disappears after 12-24 hours. This may not
have anything to do with the most recent changes. I haven't yet tested
any earlier snapshots.
Testing this is a very slow process, since I don't know how to produce
the problem; I just have to wait and see if emacs will die.
I tried to get some information by running emacs under gdb the most
recent time I started it, but all I got was this:
(gdb) c
Continuing.
[Inferior 1 (process 8196) exited with code 05400]
(gdb) bt
No stack
Does that exit code mean anything to you? I couldn't find anything by
googling.
Ken
--
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:[~2012-08-02 14:53 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-24 21:30 marco atzeri
2012-06-25 4:31 ` Christopher Faylor
2012-06-25 7:35 ` marco atzeri
2012-06-25 8:07 ` Corinna Vinschen
2012-06-25 8:38 ` marco atzeri
2012-06-25 9:02 ` Corinna Vinschen
2012-06-25 9:36 ` marco atzeri
2012-06-25 11:58 ` marco atzeri
2012-06-25 14:46 ` Christopher Faylor
2012-06-25 15:01 ` marco atzeri
2012-06-25 15:29 ` Christopher Faylor
2012-06-25 16:28 ` marco atzeri
2012-06-26 11:53 ` Ken Brown
2012-06-26 14:10 ` Christopher Faylor
2012-06-26 15:04 ` Christopher Faylor
2012-06-26 15:32 ` Corinna Vinschen
2012-06-26 15:52 ` Christopher Faylor
2012-06-26 16:32 ` Achim Gratz
2012-06-26 18:51 ` marco atzeri
2012-06-26 19:24 ` Christopher Faylor
2012-06-26 19:46 ` marco atzeri
2012-06-26 19:48 ` Christopher Faylor
2012-06-26 19:55 ` marco atzeri
2012-06-26 20:15 ` Christopher Faylor
2012-06-26 20:28 ` marco atzeri
2012-06-26 20:32 ` Christopher Faylor
2012-06-26 20:51 ` marco atzeri
2012-06-26 20:53 ` Christopher Faylor
2012-06-27 1:47 ` Christopher Faylor
2012-07-02 14:43 ` marco atzeri
2012-08-01 9:43 ` Corinna Vinschen
2012-08-01 10:35 ` marco atzeri
2012-08-01 12:29 ` Corinna Vinschen
2012-08-01 12:42 ` marco atzeri
2012-08-01 12:46 ` Corinna Vinschen
2012-08-01 12:52 ` marco atzeri
2012-08-01 12:58 ` Corinna Vinschen
2012-08-01 12:46 ` Ken Brown
2012-08-01 12:59 ` Corinna Vinschen
2012-08-02 15:57 ` Ken Brown [this message]
2012-08-02 16:29 ` Corinna Vinschen
2012-08-02 17:28 ` Filipp Gunbin
2012-08-02 18:15 ` Ken Brown
2012-08-03 7:43 ` Filipp Gunbin
2012-08-02 18:21 ` Achim Gratz
2012-08-02 18:40 ` Christopher Faylor
2012-08-02 19:29 ` Achim Gratz
2012-08-02 19:42 ` Christopher Faylor
2012-08-03 3:41 ` Ken Brown
2012-08-03 7:05 ` Christopher Faylor
2012-08-03 7:49 ` Achim Gratz
2012-08-03 16:24 ` Christopher Faylor
2012-08-03 20:45 ` Ken Brown
2012-08-04 2:14 ` Christopher Faylor
2012-08-05 4:39 ` Ken Brown
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=501A946A.2030102@cornell.edu \
--to=kbrown@cornell.edu \
--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).