From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22388 invoked by alias); 6 Aug 2010 19:16:11 -0000 Received: (qmail 22367 invoked by uid 22791); 6 Aug 2010 19:16:10 -0000 X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE X-Spam-Check-By: sourceware.org Received: from mail-iw0-f169.google.com (HELO mail-iw0-f169.google.com) (209.85.214.169) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 06 Aug 2010 19:16:04 +0000 Received: by iwn10 with SMTP id 10so1895949iwn.0 for ; Fri, 06 Aug 2010 12:16:03 -0700 (PDT) Received: by 10.231.173.9 with SMTP id n9mr14132740ibz.146.1281122163138; Fri, 06 Aug 2010 12:16:03 -0700 (PDT) MIME-Version: 1.0 Received: by 10.231.184.12 with HTTP; Fri, 6 Aug 2010 12:15:43 -0700 (PDT) In-Reply-To: References: <4C5C4433.60302@gmail.com> <4C5C453D.4090704@caviumnetworks.com> <4C5C4B8A.7090303@gmail.com> From: Bruce Korb Date: Fri, 06 Aug 2010 19:16:00 -0000 Message-ID: Subject: Re: Bizarre GCC problem - how do I debug it? To: Richard Guenther Cc: Tom Tromey , David Daney , gcc@gcc.gnu.org, bug-gdb@gnu.org, insight@sourceware.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Mailing-List: contact insight-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: insight-owner@sourceware.org X-SW-Source: 2010-q3/txt/msg00024.txt.bz2 Hi Richard, On Fri, Aug 6, 2010 at 11:43 AM, Richard Guenther wrote: > The gdb version on openSUSE that ship with GCC 4.5 is perfectly fine > (it's 7.1 based). =A0No idea what the reporter is talking about (we don't= ship > insight IIRC). You are remembering correctly. I was not clear enough. I use Insight and Insight is tightly bound to a particular version of GDB. Since Insight is not distributed or supported by openSuSE, this is not an openSuSE issue. This is an Insight i= ssue (for having fallen behind, though it is understandable...) and it is a GDB (and? GCC) issue *because* the _failure_mode_is_too_confusing_. GDB/GCC should be coordinating so that GDB looks at the binary and says, "I do not understand the debug information". Instead, GDB believes that there are no newline characters in the input. Is that a GDB issue or a GCC issue? I cannot say. What I can say is that the hapless user should be able to read an error message and know what the problem is. This does not tell me: > (gdb) b done_check > Breakpoint 5 at 0x40af44: file /usr/include/gmp.h, line 1661. Thank you everyone. Regards, Bruce