public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ices.utexas.edu>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/10512: g++ 3.2 creates multiple constructors: gdb 5.3 can't set breakpoints
Date: Tue, 29 Apr 2003 17:06:00 -0000	[thread overview]
Message-ID: <20030429170601.7759.qmail@sources.redhat.com> (raw)

The following reply was made to PR c++/10512; it has been noted by GNATS.

From: Wolfgang Bangerth <bangerth@ices.utexas.edu>
To: Joachim Eibl <joachim.eibl@gmx.de>
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: c++/10512: g++ 3.2 creates multiple constructors: gdb 5.3 can't
 set breakpoints
Date: Tue, 29 Apr 2003 12:01:03 -0500 (CDT)

 > I mainly posted this in the gcc-bug-database because the mention of the
 > gdb-problem wasn't there yet. IMHO the gcc-developers should be aware
 > that their changes also can break gdb-functionality.
 
 I bet they are :-)
 
 > As a user I expect that these tools work together.
 
 I think we are all aware of this and agree that it is a bug. Given limited 
 resources in a volunteer project, it seems as if just nobody ever got 
 around to fixing this. You are invited to generate a patch!
 
 
 > I didn't really understand this at first. Probably I should rather have
 > added a note instead of opening a new report - sorry for any
 > inconvenience. (Why does adding a note require the use of email, when
 > starting a new report does not?)
 
 There's a button "Send mail to interested parties" in GNATS, that allows 
 you to attach a note to an existing report.
 
 I would suggest the following: Can you please send a brief summary of this 
 bug report to the audit trail of one of the other two PRs you cite (the 
 one that matches best)? I'll close this one, since there is really no good 
 reason to force those who can fix bugs to search through the entire 
 database.
 
 W.
 
 -------------------------------------------------------------------------
 Wolfgang Bangerth              email:            bangerth@ices.utexas.edu
                                www: http://www.ices.utexas.edu/~bangerth/
 
 
 


             reply	other threads:[~2003-04-29 17:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-29 17:06 Wolfgang Bangerth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-04-29 17:01 bangerth
2003-04-28 14:32 bangerth
2003-04-27 12:16 joachim.eibl

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=20030429170601.7759.qmail@sources.redhat.com \
    --to=bangerth@ices.utexas.edu \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).