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
Date:	Thu, 22 Feb 2001 14:51:17 -0500
From:	Christopher Faylor <cgf AT redhat DOT com>
To:	Earnie Boyd <cygwin AT cygwin DOT com>
Subject:	Re: GCC untrackable crashes
Message-ID:	<20010222145117.A20371@redhat.com>
Mail-Followup-To:	Earnie Boyd <cygwin AT cygwin DOT com>
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> <3A956144 DOT 76EC3610 AT yahoo DOT com>
Mime-Version:	1.0
User-Agent:	Mutt/1.3.11i
In-Reply-To:	<3A956144.76EC3610@yahoo.com>; from earnie_boyd@yahoo.com on Thu, Feb 22, 2001 at 01:58:12PM -0500

On Thu, Feb 22, 2001 at 01:58:12PM -0500, Earnie Boyd wrote:
>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.

I guess I am getting sort of tired of workarounds.  It is increasingly
discouraging to read this mailing list.  There are lots of advisors,
which is nice, but very very few workers, which is... discouraging.

Giving someone the advice of "Yeah, gdb is broke -- just use assembly
language" is just not going to make my day.

cgf

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

- Raw text -