Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Benjamin Kosnik <bkoz@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: Jason Merrill <jason@redhat.com>,
	libstdc++@gcc.gnu.org, gdb@sources.redhat.com
Subject: Re: C++ debugging progress
Date: Thu, 29 Nov 2001 12:50:00 -0000	[thread overview]
Message-ID: <Pine.SOL.3.91.1011129124607.4457B-100000@taarna.cygnus.com> (raw)
In-Reply-To: <20011129152709.A9719@nevyn.them.org>

I'd like to give this work a spin when it gets in. Jason, I see that 
you've not posted to gcc-patches with this: can you let me know when it's 
in mainline gcc? I figure it's pretty pointless to try this without 
the gdb bits. Daniel, same with you, except gdb-patches.

thanks again to both of you,
benjamin

> To be honest, I'd rather the patch go in anyway.  C++ debugging for v3
> is so broken in gdb 5.1 that it does not make a lot of sense to cater
> to it.


WARNING: multiple messages have this Message-ID

From: Benjamin Kosnik <bkoz@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: Jason Merrill <jason@redhat.com>,
	libstdc++@gcc.gnu.org, gdb@sources.redhat.com
Subject: Re: C++ debugging progress
Date: Sun, 25 Nov 2001 08:40:00 -0000	[thread overview]
Message-ID: <Pine.SOL.3.91.1011129124607.4457B-100000@taarna.cygnus.com> (raw)
Message-ID: <20011125084000.gQ2xPYP2jeg0ZZwF-vdly3rWM0dmWO4k8muAX8W0Yl0@z> (raw)
In-Reply-To: <20011129152709.A9719@nevyn.them.org>


I'd like to give this work a spin when it gets in. Jason, I see that 
you've not posted to gcc-patches with this: can you let me know when it's 
in mainline gcc? I figure it's pretty pointless to try this without 
the gdb bits. Daniel, same with you, except gdb-patches.

thanks again to both of you,
benjamin

> To be honest, I'd rather the patch go in anyway.  C++ debugging for v3
> is so broken in gdb 5.1 that it does not make a lot of sense to cater
> to it.


  parent reply	other threads:[~2001-11-29 12:50 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-27 23:03 Daniel Jacobowitz
2001-11-18 21:43 ` Daniel Jacobowitz
2001-11-19  9:04 ` Benjamin Kosnik
2001-11-27 23:36   ` Benjamin Kosnik
2001-11-19 11:16 ` Daniel Berlin
2001-11-21 13:37   ` Dan Mosedale
2001-11-28 12:25     ` Dan Mosedale
2001-11-27 23:43   ` Daniel Berlin
2001-11-19 13:41 ` Jason Merrill
2001-11-28  1:31   ` Jason Merrill
2001-11-28  9:41   ` Daniel Jacobowitz
2001-11-21  4:12     ` Daniel Jacobowitz
2001-11-21  5:06     ` Daniel Berlin
2001-11-28 10:36       ` Daniel Berlin
2001-11-28 10:49       ` Daniel Jacobowitz
2001-11-21 12:33         ` Daniel Jacobowitz
2001-11-28 11:41     ` Jason Merrill
2001-11-21 13:21       ` Jason Merrill
2001-11-21 13:42       ` Daniel Jacobowitz
2001-11-28 12:32         ` Daniel Jacobowitz
2001-11-21 16:38       ` Jason Merrill
2001-11-22  0:13         ` Daniel Jacobowitz
2001-11-24 22:52           ` Jason Merrill
2001-11-29  9:44             ` Jason Merrill
2001-11-29 12:28             ` Daniel Jacobowitz
2001-11-25  8:34               ` Daniel Jacobowitz
2001-11-25  9:01               ` Kevin Buettner
2001-11-25 10:30                 ` Jason Merrill
2001-11-29 19:12                   ` Jason Merrill
2001-11-29 13:11                 ` Kevin Buettner
2001-11-29 12:50               ` Benjamin Kosnik [this message]
2001-11-25  8:40                 ` Benjamin Kosnik
2001-11-28 13:31           ` Daniel Jacobowitz
2001-11-28 13:03         ` Jason Merrill
     [not found]       ` <20011128151819.A31514@nevyn.them.org>
2001-11-21 22:26         ` Jason Merrill
2001-11-28 13:14           ` Jason Merrill

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=Pine.SOL.3.91.1011129124607.4457B-100000@taarna.cygnus.com \
    --to=bkoz@redhat.com \
    --cc=drow@mvista.com \
    --cc=gdb@sources.redhat.com \
    --cc=jason@redhat.com \
    --cc=libstdc++@gcc.gnu.org \
    /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