Robert Collins wrote:
Max, I suggest making clean, then makeing with 'CXXFLAGS=-g -O0.
Then, the call stack may have more detail.
Anyway, as I can't reprodiuce this, I'm limited to throwing peanuts :}.
Unfortunately, I can't persuade the -O0 version to crash at all.
This looks like a long
- Original Message -
From: Max Bowsher [EMAIL PROTECTED]
To: Robert Collins [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Thursday, March 27, 2003 12:44 PM
Subject: Re: setup crashes - backtrace
Robert Collins wrote:
Max, I suggest making clean, then makeing with 'CXXFLAGS=-g -O0
On Wed, 26 Mar 2003, Max Bowsher wrote:
Here is the Dr. MinGW output for the at-startup crash being mentioned on
[EMAIL PROTECTED]
setup-2.340.2.3.debug.exe caused an Access Violation at location 78403330
Reading from location 78403330.
Registers:
eax=0077 ebx=0022f930
On Thu, 27 Mar 2003, Vince Hoffman wrote:
If this is usefull (unlikely as i'm no programmer but hey ;)
from gdb with the snapshot i got.
(gdb) run
Starting program: /tmp/setup-2.340.2.3.exe
warning: LOG: 2 Starting cygwin install, version 2.340.2.3
warning: LOG: 2 Current Directory:
On Thu, 2003-03-27 at 23:44, Max Bowsher wrote:
Robert Collins wrote:
Max, I suggest making clean, then makeing with 'CXXFLAGS=-g -O0.
Then, the call stack may have more detail.
Anyway, as I can't reprodiuce this, I'm limited to throwing peanuts :}.
Unfortunately, I can't persuade
Here is the Dr. MinGW output for the at-startup crash being mentioned on
[EMAIL PROTECTED]
setup-2.340.2.3.debug.exe caused an Access Violation at location 78403330
Reading from location 78403330.
Registers:
eax=0077 ebx=0022f930 ecx=77f51b2b edx=004961bc esi=0022fe70
edi=0022fe10
Max Bowsher wrote:
Here is the Dr. MinGW output for the at-startup crash being mentioned on
[EMAIL PROTECTED]
setup-2.340.2.3.debug.exe caused an Access Violation at location 78403330
Reading from location 78403330.
Registers:
eax=0077 ebx=0022f930 ecx=77f51b2b edx=004961bc esi=0022fe70
