X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Wed, 6 Jul 2011 09:09:40 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: Debug info broken for gcc-4.5.0 (experimental) Message-ID: <20110706070940.GB23717@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <4E13FB75 DOT 3050504 AT cs DOT utoronto DOT ca> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <4E13FB75.3050504@cs.utoronto.ca> User-Agent: Mutt/1.5.21 (2010-09-15) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On Jul 6 02:06, Ryan Johnson wrote: > Hi all, > > I've been using gcc-4.5.0 happily for a while, but today I had to > break out gdb to chase down a seg fault. Unfortunately, gdb was > getting line numbers completely wrong, so I had to revert to gcc-4.3 > to work through my bug. > > Has anybody else seen this? If not, and if it's not trivial to > reproduce, I can cook up a minimal test case. The debug info in gcc-4.5 has changed in a way which older GDBs don't understand. You can build GDB 7.2 yourself, that should help. Actually, Chris, we're still on GDB 6.8. Any chance we can get an official 7.2 release? Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple