Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <009101c2f3ea$5511ec50$5300a8c0@pomello>
From: "Max Bowsher" <maxb AT ukf DOT net>
To: "Robert Collins" <rbcollins AT cygwin DOT com>
Cc: <cygwin AT cygwin DOT com>
References: <1048679085 DOT 9951 DOT 11 DOT camel AT localhost> <01b601c2f3ab$d9caa9d0$0a00010a AT unsane DOT co DOT uk> <1048714873 DOT 9946 DOT 37 DOT camel AT localhost> <001501c2f3e4$659e9560$5300a8c0 AT pomello> <3E8227E0 DOT 2060808 AT cygwin DOT com>
Subject: Re: Corrected: setup.exe beta (testing needed - really!)
Date: Wed, 26 Mar 2003 22:52:07 -0000
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106

Robert Collins wrote:
> Max Bowsher wrote:
>> Robert Collins wrote:
>>
>>> On Thu, 2003-03-27 at 02:24, Vince Hoffman wrote:
>>>
>>>> Havent a clean system to try a full install. however on running it to
>>>> upgrade/add packages  the first run crashed .
>>>> on the second run all was fine and componants were added/updated
>>>> perfectly. I tried running a few more times to reproduce the crash and
>>>> on average about one in 5 times (very rough average) it crashed.(see
>>>> attached drwatson crashlog) for log of 2 of these crashes.
>>
>>
>> I'm getting this too - but only on my desktop - not my laptop.
>>
>> Crash frequency is only 1 in 20, as well.
>>
>>
>>> Ok, well this is 'not good' :}.
>>>
>>> At what point does it crash?
>>
>>
>> Before the splash page appears.
>
> Ah. Can you reproduce it under gdb? If not, can you generate the line
> numbers from the addresses in the backtrace (hint: fire up gdb, load the
> .exe that you used to provoke the problem, and then
> list *0x000223344 )

No, can't reproduce inside gdb.

The address of the crash is in the system DLL area.

I will download Dr. MinGW, and try to get a backtrace that way.

I suggest relocating this thread to cygwin-apps. I will post my next message
there, unless told otherwise.

Max.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/