On 8/3/2012 7:48 PM, Christopher Faylor wrote:
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
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 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:
Christophe
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 t
Christopher Faylor cygwin.com> writes:
> Thanks. I think I see the problem but I won't be able to get to it tonight.
Based on that information, I went back to the July 29th snapshot and it is
holding up good so far. I checked my logs and I had the snapshot from July 25th
installed before going
Ken Brown writes:
> On 8/2/2012 12:28 PM, Filipp Gunbin wrote:
>> Ken Brown writes:
>>
>> ...
>>> 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 h
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
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 c
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 ru
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
On Thu, Aug 02, 2012 at 08:11:31PM +0200, Achim Gratz wrote:
>Ken Brown writes:
>> 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
Ken Brown writes:
> 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 tes
On 8/2/2012 12:28 PM, Filipp Gunbin wrote:
Ken Brown writes:
...
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 snapshot
Ken Brown writes:
...
> 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.
...
Hi Ken,
I observe Emacs cr
On Aug 2 10:53, Ken Brown wrote:
> On 8/1/2012 8:58 AM, Corinna Vinschen wrote:
> >On Aug 1 08:46, Ken Brown wrote:
> >>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. Bu
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, Christo
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:
> >
On Aug 1 14:51, marco atzeri wrote:
> On 8/1/2012 2:46 PM, Corinna Vinschen wrote:
>
> >>
> >>just lucky, I cleaned everything expect a forgotten test directory..
> >
> >Sorry if I'm dense, but does that mean you could reproduce the crash
> >now again?
> >
> >
> >Corinna
> >
>
> No crash.
> Just
On 8/1/2012 2:46 PM, Corinna Vinschen wrote:
just lucky, I cleaned everything expect a forgotten test directory..
Sorry if I'm dense, but does that mean you could reproduce the crash
now again?
Corinna
No crash.
Just that the test case was still available and I was able to provide
a very
On Aug 1 14:41, marco atzeri wrote:
> On 8/1/2012 2:29 PM, Corinna Vinschen wrote:
> >On Aug 1 12:34, marco atzeri wrote:
>
> >>
> >>$ 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!
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 up
On 8/1/2012 2:29 PM, Corinna Vinschen wrote:
On Aug 1 12:34, marco atzeri wrote:
$ 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...
Corinna
just lucky, I cleane
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 st
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 snapshot
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
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
Thanks
Marco
--
Problem reports: http://cygwin.com/problems.html
FAQ: htt
On Tue, Jun 26, 2012 at 04:53:31PM -0400, Christopher Faylor wrote:
>On Tue, Jun 26, 2012 at 10:50:51PM +0200, marco atzeri wrote:
>>On 6/26/2012 10:32 PM, Christopher Faylor wrote:
>>
> I'm crossing my fingers that the latest CVS version of Cygwin fixes
> your problem and I won't have to d
On Tue, Jun 26, 2012 at 10:50:51PM +0200, marco atzeri wrote:
>On 6/26/2012 10:32 PM, Christopher Faylor wrote:
>
I'm crossing my fingers that the latest CVS version of Cygwin fixes
your problem and I won't have to download this anyway.
>>>
>>> building from CVS, I will let you know
>>
>>
On 6/26/2012 10:32 PM, Christopher Faylor wrote:
I'm crossing my fingers that the latest CVS version of Cygwin fixes
your problem and I won't have to download this anyway.
building from CVS, I will let you know
Please use the snapshot, not your own build.
cgf
I was planning both, just in
On Tue, Jun 26, 2012 at 10:28:04PM +0200, marco atzeri wrote:
>On 6/26/2012 10:14 PM, Christopher Faylor wrote:
>>
>> Can you still duplicate this problem with today's snapshot?
>
>20110626 was still failing, I will recheck anyway
>
>>
>>
>> I get a:
>>
>> Error 403
>> You can't access to the reque
On 6/26/2012 10:14 PM, Christopher Faylor wrote:
Can you still duplicate this problem with today's snapshot?
20110626 was still failing, I will recheck anyway
I get a:
Error 403
You can't access to the requested page or directory.
I can download the other two files.
adjusted permissio
On Tue, Jun 26, 2012 at 03:47:55PM -0400, Christopher Faylor wrote:
>On Tue, Jun 26, 2012 at 03:23:57PM -0400, Christopher Faylor wrote:
>>I'll say it again: I see no difference in behavior with any snapshot or
>>with the shipping version. They all stress the system and eventually
>>require me to
On 6/26/2012 9:47 PM, Christopher Faylor wrote:
On Tue, Jun 26, 2012 at 03:23:57PM -0400, Christopher Faylor wrote:
I'll say it again: I see no difference in behavior with any snapshot or
with the shipping version. They all stress the system and eventually
require me to power cycle it.
I had
On Tue, Jun 26, 2012 at 03:23:57PM -0400, Christopher Faylor wrote:
>I'll say it again: I see no difference in behavior with any snapshot or
>with the shipping version. They all stress the system and eventually
>require me to power cycle it.
I had a "mingw-gcc" shell script in /usr/bin which seem
On 6/26/2012 9:23 PM, Christopher Faylor wrote:
It stresses a bit the computer, but on snapshot 20110619 and later CVS
the side effect is to crash all mintty sessions on my W7/64 and
to block cgf's one.
I'll say it again: I see no difference in behavior with any snapshot or
with the shipping v
On Tue, Jun 26, 2012 at 08:51:30PM +0200, marco atzeri wrote:
>On 6/26/2012 5:31 PM, Corinna Vinschen wrote:
>> On Jun 26 11:04, Christopher Faylor wrote:
>>> On Tue, Jun 26, 2012 at 10:10:28AM -0400, Christopher Faylor wrote:
On Tue, Jun 26, 2012 at 07:53:05AM -0400, Ken Brown wrote:
> On
On 6/26/2012 5:31 PM, Corinna Vinschen wrote:
On Jun 26 11:04, Christopher Faylor wrote:
On Tue, Jun 26, 2012 at 10:10:28AM -0400, Christopher Faylor wrote:
On Tue, Jun 26, 2012 at 07:53:05AM -0400, Ken Brown wrote:
On 6/24/2012 5:30 PM, marco atzeri wrote:
while building latest atlas I hit a
Christopher Faylor writes:
> Weird. I see nothing like that.
>
> I get the same behavior with the supposedly working snapshot and with the
> snapshot for which problems are reported. And with 1.7.15.
Besides the problems reported, the June 19 snapshot kills mintty
processes for me once or twice
On Tue, Jun 26, 2012 at 05:31:54PM +0200, Corinna Vinschen wrote:
>On Jun 26 11:04, Christopher Faylor wrote:
>> On Tue, Jun 26, 2012 at 10:10:28AM -0400, Christopher Faylor wrote:
>> >On Tue, Jun 26, 2012 at 07:53:05AM -0400, Ken Brown wrote:
>> >>On 6/24/2012 5:30 PM, marco atzeri wrote:
>> >>> w
On Jun 26 11:04, Christopher Faylor wrote:
> On Tue, Jun 26, 2012 at 10:10:28AM -0400, Christopher Faylor wrote:
> >On Tue, Jun 26, 2012 at 07:53:05AM -0400, Ken Brown wrote:
> >>On 6/24/2012 5:30 PM, marco atzeri wrote:
> >>> while building latest atlas I hit a bug that is crashing all the running
On Tue, Jun 26, 2012 at 10:10:28AM -0400, Christopher Faylor wrote:
>On Tue, Jun 26, 2012 at 07:53:05AM -0400, Ken Brown wrote:
>>On 6/24/2012 5:30 PM, marco atzeri wrote:
>>> while building latest atlas I hit a bug that is crashing all the running
>>> cygwin process.
>>> It crashes on 20120619 sna
On Tue, Jun 26, 2012 at 07:53:05AM -0400, Ken Brown wrote:
>On 6/24/2012 5:30 PM, marco atzeri wrote:
>> while building latest atlas I hit a bug that is crashing all the running
>> cygwin process.
>> It crashes on 20120619 snapshot and also latest cvs source.
>> No issue on 20120611 snapshot.
>
>I'
On 6/24/2012 5:30 PM, marco atzeri wrote:
while building latest atlas I hit a bug that is crashing all the running
cygwin process.
It crashes on 20120619 snapshot and also latest cvs source.
No issue on 20120611 snapshot.
I'm also seeing this crash, but it does not kill all running cygwin
proc
On 6/25/2012 5:29 PM, Christopher Faylor wrote:
On Mon, Jun 25, 2012 at 05:00:57PM +0200, marco atzeri wrote:
On 6/25/2012 4:45 PM, Christopher Faylor wrote:
On Mon, Jun 25, 2012 at 01:57:26PM +0200, marco atzeri wrote:
On 6/25/2012 11:36 AM, marco atzeri wrote:
On 6/25/2012 11:00 AM, Corinna
On Mon, Jun 25, 2012 at 05:00:57PM +0200, marco atzeri wrote:
>On 6/25/2012 4:45 PM, Christopher Faylor wrote:
>> On Mon, Jun 25, 2012 at 01:57:26PM +0200, marco atzeri wrote:
>>> On 6/25/2012 11:36 AM, marco atzeri wrote:
On 6/25/2012 11:00 AM, Corinna Vinschen wrote:
> On Jun 25 10:37, m
On 6/25/2012 4:45 PM, Christopher Faylor wrote:
On Mon, Jun 25, 2012 at 01:57:26PM +0200, marco atzeri wrote:
On 6/25/2012 11:36 AM, marco atzeri wrote:
On 6/25/2012 11:00 AM, Corinna Vinschen wrote:
On Jun 25 10:37, marco atzeri wrote:
A normal exception should kill just the running process
On Mon, Jun 25, 2012 at 01:57:26PM +0200, marco atzeri wrote:
>On 6/25/2012 11:36 AM, marco atzeri wrote:
>> On 6/25/2012 11:00 AM, Corinna Vinschen wrote:
>>> On Jun 25 10:37, marco atzeri wrote:
A normal exception should kill just the running process, while
I see that xprobe_comp,
On 6/25/2012 11:36 AM, marco atzeri wrote:
On 6/25/2012 11:00 AM, Corinna Vinschen wrote:
On Jun 25 10:37, marco atzeri wrote:
A normal exception should kill just the running process, while
I see that xprobe_comp, bash, mintty are killed and
also others bash and mintty processes are taking do
On 6/25/2012 11:00 AM, Corinna Vinschen wrote:
On Jun 25 10:37, marco atzeri wrote:
A normal exception should kill just the running process, while
I see that xprobe_comp, bash, mintty are killed and
also others bash and mintty processes are taking down.
Really all processes or just all proce
On Jun 25 10:37, marco atzeri wrote:
> On 6/25/2012 10:05 AM, Corinna Vinschen wrote:
> >On Jun 25 09:34, marco atzeri wrote:
> >>I tried to strace but it produces an enormous amount of data
> >>
> >>$ ls -sh1 xprobe_comp.strace*
> >>330M xprobe_comp.strace_fail
> >>761M xprobe_comp.strace_good
>
On 6/25/2012 10:05 AM, Corinna Vinschen wrote:
On Jun 25 09:34, marco atzeri wrote:
On 6/25/2012 6:31 AM, Christopher Faylor wrote:
On Sun, Jun 24, 2012 at 11:30:02PM +0200, marco atzeri wrote:
Cgf, Corinna,
while building latest atlas I hit a bug that is crashing all the
running cygwin proc
On Jun 25 09:34, marco atzeri wrote:
> On 6/25/2012 6:31 AM, Christopher Faylor wrote:
> >On Sun, Jun 24, 2012 at 11:30:02PM +0200, marco atzeri wrote:
> >>Cgf, Corinna,
> >>
> >>while building latest atlas I hit a bug that is crashing all the
> >>running cygwin process.
> >>It crashes on 20120619
On 6/25/2012 6:31 AM, Christopher Faylor wrote:
On Sun, Jun 24, 2012 at 11:30:02PM +0200, marco atzeri wrote:
Cgf, Corinna,
while building latest atlas I hit a bug that is crashing all the
running cygwin process.
It crashes on 20120619 snapshot and also latest cvs source.
No issue on 20120611
On Sun, Jun 24, 2012 at 11:30:02PM +0200, marco atzeri wrote:
>Cgf, Corinna,
>
>while building latest atlas I hit a bug that is crashing all the
>running cygwin process.
>It crashes on 20120619 snapshot and also latest cvs source.
>No issue on 20120611 snapshot.
>
>The binary to replicate and a e
Cgf, Corinna,
while building latest atlas I hit a bug that is crashing all the
running cygwin process.
It crashes on 20120619 snapshot and also latest cvs source.
No issue on 20120611 snapshot.
The binary to replicate and a extract of the strace's is at
http://matzeri.altervista.org/works/atl
55 matches
Mail list logo
