From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-19189-listarch-gdb=sources.redhat.com@sources.redhat.com>
Received: (qmail 7875 invoked by alias); 24 Aug 2004 17:54:45 -0000
Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:gdb-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/gdb/>
List-Post: <mailto:gdb@sources.redhat.com>
List-Help: <mailto:gdb-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: gdb-owner@sources.redhat.com
Received: (qmail 7775 invoked from network); 24 Aug 2004 17:54:41 -0000
Received: from unknown (HELO maynard.mail.mindspring.net) (207.69.200.243)
  by sourceware.org with SMTP; 24 Aug 2004 17:54:41 -0000
Received: from user-119a90a.biz.mindspring.com ([66.149.36.10] helo=berman.michael-chastain.com)
	by maynard.mail.mindspring.net with esmtp (Exim 3.33 #1)
	id 1BzfVG-0006a2-00; Tue, 24 Aug 2004 13:54:38 -0400
Received: from mindspring.com (localhost [127.0.0.1])
	by berman.michael-chastain.com (Postfix) with SMTP
	id 7C5404B102; Tue, 24 Aug 2004 13:54:56 -0400 (EDT)
Date: Tue, 24 Aug 2004 17:54:00 -0000
From: Michael Chastain <mec.gnu@mindspring.com>
To: drow@false.org, dan@imi-test.com
Subject: Re: cannot subscript something of type <data variable, no debug info>
Cc: gdb@sources.redhat.com
Message-ID: <412B80EF.nailIRH13Q2GM@mindspring.com>
References: <005601c4871d$67c8c9f0$0401a8c0@dan>
 <20040821021144.GA3321@nevyn.them.org>
 <008d01c48952$b7e0e7b0$0401a8c0@dan>
 <412A616D.nailD4K28EC6E@mindspring.com>
 <009e01c48959$a5192640$0401a8c0@dan>
 <412B30D2.nailETK1H2VST@mindspring.com>
 <00d701c489fb$0854d370$0401a8c0@dan>
 <20040824165533.GA31796@nevyn.them.org>
 <412B78D8.nailIPD1ZS2MK@mindspring.com>
 <00e001c48a01$014b02b0$0401a8c0@dan>
In-Reply-To: <00e001c48a01$014b02b0$0401a8c0@dan>
User-Agent: nail 10.8 6/28/04
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-SW-Source: 2004-08/txt/msg00336.txt.bz2

Well, it's a relief that the more recent version is the version that
doesn't exhibit the buggy behavior.  It might be a SuSE gcc packaging
bug, or it might be an installation bug on your side.  We'll never know.

> At this point, tho, I might as well just stick with the 3.3.4 update,
> do you agree??  I'm already compiling it anyway...

Try it; see if it works for you.

Make sure to configure with "--prefix=..." so that you can install
it side by side without disturbing your vendor installation.