From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: crash on latest cygwin snapshot
Date: Sat, 04 Aug 2012 02:14:00 -0000 [thread overview]
Message-ID: <20120803234809.GA18316@ednor.casa.cgf.cx> (raw)
In-Reply-To: <501C2E54.6080603@cornell.edu>
On Fri, Aug 03, 2012 at 04:02:28PM -0400, Ken Brown wrote:
>On 8/3/2012 12:21 PM, Christopher Faylor wrote:
>> On Thu, Aug 02, 2012 at 11:41:19PM -0400, Christopher Faylor wrote:
>>> On Thu, Aug 02, 2012 at 11:05:10PM -0400, Ken Brown wrote:
>>>> On 8/2/2012 3:34 PM, Christopher Faylor wrote:
>>>>> On Thu, Aug 02, 2012 at 09:14:50PM +0200, Achim Gratz wrote:
>>>>>> Christopher Faylor writes:
>>>>>>> Just to be clear: Is this with the recent snapshot?
>>>>>>
>>>>>> Yes, this is with the 2012-08-01 snapshot.
>>>>>>
>>>>>>> I ask because one other "I see something similar" seemed to come from
>>>>>>> 1.7.16.
>>>>>>
>>>>>> I'm almost always running a snapshot, but I can back it out to vanilla
>>>>>> Cygwin or any other snapshot if it helps finding the error. I don't
>>>>>> think I've had any other updates except mesa inbetween switching from
>>>>>> the snapshot I used before and the current one ??? but that is
>>>>>> circumstancial evidence only.
>>>>>
>>>>> It would be interesting to see if you or Ken have a problem with the
>>>>> 20120730 snapshot.
>>>>>
>>>>> And, if so, then an strace would probably be useful, although it would
>>>>> be huge. If you do get one, let me know how to download it or I can
>>>>> provide temporary storage somewhere.
>>>>
>>>> I do have the same problem with the 20120730 snapshot. I started emacs
>>>> in an xterm window, attached strace, and walked away. This time it
>>>> didn't take long for emacs to crash, so the strace output isn't huge:
>>>>
>>>> wget http://sanibeltranquility.com/cygwin/strace.out
>>>
>>> Thanks. I think I see the problem but I won't be able to get to it
>>> tonight.
>>>
>>> It's in the new signal handling code.
>>
>> I was actually able to duplicate this fairly easy. It took me too long
>> to realize that I had to run the X version of emacs, when that should
>> have been obvious from the strace.
>>
>> I have uploaded a new snapshot which should fix the problem.
>>
>> Can you confirm Ken?
>
>I'm testing. It looks good so far, but I'd like to get emacs running
>without a crash for 24 hours before I'm confident. I'll report back
>tomorrow.
>
>I'm also testing to see if the recent changes have fixed the problem
>that I was struggling with in
>http://cygwin.com/ml/cygwin-xfree/2012-04/msg00048.html . That also
>looks good so far.
Well, fingers crossed, but I'm not aware of anything which would fix what
you describe there.
cgf
--
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-03 23:48 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
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 [this message]
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=20120803234809.GA18316@ednor.casa.cgf.cx \
--to=cgf-use-the-mailinglist-please@cygwin.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).