Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Dan Conti <danc@fullplaymedia.com>
Cc: gdb@sources.redhat.com
Subject: Re: debugging gcc 3.x c++
Date: Tue, 12 Feb 2002 16:53:00 -0000	[thread overview]
Message-ID: <20020212195322.A7646@nevyn.them.org> (raw)
In-Reply-To: <D8DFF0AFE792914996F997E68FEC3A48F597@bunker.iobjects.com>

On Tue, Feb 12, 2002 at 03:02:55PM -0800, Dan Conti wrote:
> > -----Original Message-----
> > From: Daniel Jacobowitz [mailto:drow@mvista.com]
> > Subject: Re: debugging gcc 3.x c++
> >
> > [snip]
> >
> > This is fixed in GDB CVS.  It has been for a bit over a month now. 
> > Could you give it a try?
> > 
> > I see on the PR trail that I told you this at the time.  The
> > misunderstanding may come from 5.1.1 being released afterwards; that
> > does NOT contain the fix.  5.2 will.
> 
> Yes, i remember you telling me that at the time. I tried out a snap from
> 01/22/02 which seemed to fix it but showed other issues on my target.
> When 5.1.1 came out, i figured that the existing bugfixes would be
> incorporated into that release, and when i ran it initially it didn't
> seem to exhibit this problem (although that could easily be attributed
> to different test code). Out of curiosity, why wasn't this incorporated
> into the 5.1.1 release?

Because the 5.1.1 release was a maintenance release, not off the
development branch.  It mostly incorporated copyright and legal fixes,
and one DWARF-2 feature.  What other issues?

> In any case, when is gdb 5.2 scheduled to be released? If it was just
> me, i'd use a cvs snapshot, but i have to set this up for a group of
> people and i'd rather use something more stable. Alternatively, would it
> be possible for me to patch my 5.1.1 with the appropriate fixes?

In two months, I believe.  It'd be possible, but quite a lot of work.

> > Actually, it's for GNATS use only.  GNATS messages get copied there.
> 
> Then perhaps the web page should be updated to mention that it's for
> GNATS use only? The description indicates that it can be used for
> discussing bugs submitted to the database, so one would think that
> discussion this bug (which was submitted to the database) should happen
> on that list.

Yes, probably.

-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2002-02-13  0:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-12 15:02 Dan Conti
2002-02-12 16:53 ` Daniel Jacobowitz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-02-12 14:00 Dan Conti
2002-02-12 14:33 ` Daniel Jacobowitz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20020212195322.A7646@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=danc@fullplaymedia.com \
    --cc=gdb@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox