delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2001/02/22/14:22:27

Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
X-Apparently-From: <earnie?boyd AT yahoo DOT com>
Message-ID: <3A956144.76EC3610@yahoo.com>
Date: Thu, 22 Feb 2001 13:58:12 -0500
From: Earnie Boyd <earnie_boyd AT yahoo DOT com>
Reply-To: Earnie Boyd <cygwin AT cygwin DOT com>
X-Mailer: Mozilla 4.76 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: GCC untrackable crashes
References: <711F6B80B5B4D211BA900090272AB7649C4211 AT noyce DOT eecs DOT berkeley DOT edu> <20010221221500 DOT A8646 AT redhat DOT com> <3A951897 DOT B84D8F6C AT yahoo DOT com> <20010222105118 DOT C11175 AT redhat DOT com>

Christopher Faylor wrote:
> 
> On Thu, Feb 22, 2001 at 08:48:07AM -0500, Earnie Boyd wrote:
> >Christopher Faylor wrote:
> >>
> >> On Wed, Feb 21, 2001 at 06:43:40PM -0800, Kevin Camera wrote:
> >> >Thanks for the tip.  In fact, the debugger was in thread 1, and the only
> >> >other thread did not offer any other information.  So unfortunately the
> >> >problem was with the compiler or debugger, since all threads had no trace
> >> >information.
> >>
> >> Hmm.  As someone who uses the compiler and debugger on an almost daily basis
> >> I have to say that I have never seen this behavior on a program that was
> >> compiled with debugging info (-g).
> >>
> >
> >Well, I can't say that I use GDB that often but everytime that I've used
> >it I see this problem.  I've been able to switch to the assembler
> >listing and set breakpoints on each instruction of the object containing
> >main() and be able to get a source code point of problem.
> 
> I'm not interested in fixing the GDB problem.  It works fine for me when
> I need it.
> 
> If someone wants to track this down, more power to them.
> 
> I assume it has something to do with the frame pointer not being set.
> 
> I'm beginning to wonder if the rumors of Cygwin's death are not
> exaggerated if two notable Cygwin contributors have resorted to sending
> "me too" and "here's a simple test case, hope that helps" messages.
> 

Geesh, if you take the time to reread my post you'll see that I was
offering Kevin a possible work around.

> Corinna (and Chuck and Egor) and I can't do everything.  If you want a
> fix for the problem, roll up your sleeves and fix it!
> 

Nor was I asking you too.

> cgf
> 
> (This post will now be followed by the obligatory "I would look into this
> but I don't know how to debug gdb" or "I really don't have the time"
> excuses.)
> 

I don't currently have the time to get a round tuit, ;^) especially
since I can work around it.

Earnie.

_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com


--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019