Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] gcc debug option

Wascana will be using the newest 4.5 compilers. Dwarf-2 is all the rage there.

On Mon, Apr 5, 2010 at 9:41 AM, Pedro Alves <pedro@xxxxxxxxxxxxxxxx> wrote:
On Monday 05 April 2010 13:55:18, Ed.Swartz@xxxxxxxxx wrote:
> > > I think it can be safely said that DWARF-2 is significantly better
> > > than STABS as far as the quality and scope of information. Should we
> > > not change the wizard so that -gdwarf-2 is specified instead? Is that
> > > not a better default?
> >
> > If you use a recent GCC, you'll get DWARF-2 automatically.
>
> Well, as John hints, that doesn't work for MinGW.  It has both STABS and DWARF-2 support and defaults to STABS.  And MinGW seems to be the port of choice ATM.

I think that's only true for the old 3.x compilers?  As Dan hints,
it works on MinGW with more recent compilers.  I see
gcc 4.4 based compilers in mingw.org's download section, and I
thought gcc was defaulting to dwarf for a while (a few years).

IMO, a higher level tool shouldn't be changing the compiler's
default behind the user's back; it should be the decision of the user
to override what the older compiler/toolchain's maintainers decided
was best by default.  I'd have to dig through history, but I assume
gcc 3.4.5 wasn't that much after .secrel32 was added to
binutils, and dwarf2 been made possible on mingw at all.  I'd simply
declare that to support extra features, you should get yourself a
newer toolchain, and avoid all the parsing and mantainance hassle.
FYI, gcc -v won't spit out anything related to specs in not so
ancient gccs.

Just two cents from a bystander.

--
Pedro Alves
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev


Back to the top