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 (fwd)
Date: Tue, 29 Apr 2003 16:56:00 -0000	[thread overview]
Message-ID: <20030429165601.1021.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: gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: c++/10512: g++ 3.2 creates multiple constructors: gdb 5.3 can't
 set breakpoints (fwd)
Date: Tue, 29 Apr 2003 11:48:50 -0500 (CDT)

 ---------- Forwarded message ----------
 Date: Mon, 28 Apr 2003 22:02:46 +0200
 From: Joachim Eibl <joachim.eibl@gmx.de>
 To: bangerth@dealii.org
 Subject: Re: c++/10512: g++ 3.2 creates multiple constructors: gdb 5.3
     can't set breakpoints
 
 Hi,
 
 >     As you mention, this report is basically a duplicate of the
 >     ones you cite. What is different from the information given
 >     in those that would merit keeping it open?
 
 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. As a user I expect that these tools
 work together.
 I also posted it on the gdb-bug-database, because I tried to explain it more clearly. Daniel Jacobowitz already mentions
 "cloned functions", but 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?)
 
 I also tried the current gdb-version from 04-27 which still contains the problem.
 
 One reason why I investigated the matter and posted the report was because I stumbled across this problem several times
 and think that it is very annoying, because my program uses many constructors that do a lot of work and I can't simply
 step in as in the example I mentioned. (By the way: I'm author of KDiff3 at http://kdiff3.sourceforge.net). There I
 think is another gdb-problem, but I haven't investigated and simplyfied it yet.
 
 Let me end by thanking you developers for doing such an awesome job in providing such an advanced tool and supporting so
 many languages and platforms.
 
 Best regards,
 Joachim
 
 ----- Original Message -----
 From: <bangerth@dealii.org>
 To: <gcc-bugs@gcc.gnu.org>; <gcc-prs@gcc.gnu.org>; <joachim.eibl@gmx.de>; <nobody@gcc.gnu.org>
 Sent: Monday, April 28, 2003 4:32 PM
 Subject: Re: c++/10512: g++ 3.2 creates multiple constructors: gdb 5.3 can't set breakpoints
 
 
 > Synopsis: g++ 3.2 creates multiple constructors: gdb 5.3 can't set breakpoints
 >
 > State-Changed-From-To: open->feedback
 > State-Changed-By: bangerth
 > State-Changed-When: Mon Apr 28 14:32:44 2003
 > State-Changed-Why:
 >     As you mention, this report is basically a duplicate of the
 >     ones you cite. What is different from the information given
 >     in those that would merit keeping it open?
 >
 >     W.
 >
 > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10512
 >
 


                 reply	other threads:[~2003-04-29 16:56 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20030429165601.1021.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).