This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [PATCH] Support for Xilinx MicroBlaze

From: Joel Brobecker <brobecker at adacore dot com>
To: Michael Eager <eager at eagercon dot com>
Cc: tromey at redhat dot com, "gdb-patches at sourceware dot org" <gdb-patches at sourceware dot org>
Date: Thu, 15 Oct 2009 10:17:55 -0700
Subject: Re: [PATCH] Support for Xilinx MicroBlaze
References: <4AD74E86.1020500@eagercon.com> <m3iqegzk0s.fsf@fleche.redhat.com> <4AD757FE.6060704@eagercon.com>

> I'm just as happy to leave this problem unfixed.  Gcc generates an
> incorrect CIE entry, which is philosophically not a good thing.
> But fixing this causes far more problems than it solves.

One of the things that we perhaps didn't consider is debugging
code compiled with a compiler other than GCC... Not sure if one
even exists, though, but that compiler might be generating correct
debugging info, which would trigger the "bug" in GDB.

Anyway, if "GCC" is unwilling to fix the problem, then GDB has to do
its best. It's disappointing when that happens, but it's not the first
time we introduce work-arounds. This one is a little harder to accept
because it causes GDB to malfunction in case of correct debugging info.
But it's still better this way, in practice.

-- 
Joel

Follow-Ups:
- Re: [PATCH] Support for Xilinx MicroBlaze
  - From: Michael Eager

References:
- [PATCH] Support for Xilinx MicroBlaze
  - From: Michael Eager
- Re: [PATCH] Support for Xilinx MicroBlaze
  - From: Tom Tromey
- Re: [PATCH] Support for Xilinx MicroBlaze
  - From: Michael Eager

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]