This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: IA32 bootstrap error
- From: Daniel Berlin <dan at cgsoftware dot com>
- To: Stan Shebs <shebs at apple dot com>
- Cc: Richard Kenner <kenner at vlsi1 dot ultra dot nyu dot edu>, <schwab at suse dot de>, <gcc at gcc dot gnu dot org>
- Date: Sun, 30 Dec 2001 18:58:35 -0500 (EST)
- Subject: Re: IA32 bootstrap error
On Sun, 30 Dec 2001, Stan Shebs wrote:
> Daniel Berlin wrote:
> >
> > On Sun, 30 Dec 2001, Richard Kenner wrote:
> >
> > > Current CVS of gdb should work.
> > >
> > > Do you really mean to require using an unreleased GDB in order to debug
> > > programs produced by GCC?
> >
> > Yes, in order to debug an unreleased version of gcc.
> > What's the problem?
> > It is expected that gdb will release a version that supports the features
> > once gcc is released (IE soon after).
>
> Users get hosed when the releases don't happen on the expected
> schedule, a common occurrence since the releases are done on a
> volunteer basis.
>
> Tying versions together is always the easy way out, which is why
> our proprietary competitors usually go that way, but I would hope
> we would set higher standards for ourselves.
We haven't tied ourselves to a version.
We've tied ourselves to a standard (dwarf2 2.0 in this csae).
This is just another place that gdb was not compliant with it.
I would hope we wouldn't lower ourselves to saying we can't produce
perfectly standard info that other debuggers support fine, simply because
gdb wasn't up to snuff.
It still isn't near full compliance, in actuality.
But history shows that gdb doesn't get fixed until gcc breaks it.
--Dan