public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Christian Ehrhardt" <ehrhardt@mathematik.uni-ulm.de>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/4966: [3.2/3.3/3.4 regression] g++ generates incorrect debugging information
Date: Sat, 11 Jan 2003 01:46:00 -0000	[thread overview]
Message-ID: <20030111014601.550.qmail@sources.redhat.com> (raw)

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

>From ehrhardt@mathematik.uni-ulm.de  Mon Jan 13 00:56:03 2003
From: "Christian Ehrhardt" <ehrhardt@mathematik.uni-ulm.de>
To: gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org,
  meixner@rbg.informatik.tu-darmstadt.de, rodrigc@gcc.gnu.org,
  gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org
Cc:  
Subject: Re: c++/4966: [3.2/3.3/3.4 regression] g++ generates incorrect debugging information
Date: Sat, 11 Jan 2003 02:38:22 +0100

 It seems that g++ emits two identical copies of the constructor
 for B from the same source lines. When gdb sets the breakpoint
 at the specified line it chooses one of those copies but gcc happens
 to call the other copy. Thus the breakpoint is never reached.
 This means that this is probably a gdb bug (gdb should set two break
 points) but someone should verify that the debugging information
 is really ok.
 
     regards  Christian
 
 -- 
 THAT'S ALL FOLKS!


             reply	other threads:[~2003-01-11  1:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-11  1:46 Christian Ehrhardt [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-02-21 17:06 Mark Mitchell
2003-02-21 14:56 Matthias Meixner
2003-02-21  2:25 mmitchel
2003-01-08  0:01 bangerth

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=20030111014601.550.qmail@sources.redhat.com \
    --to=ehrhardt@mathematik.uni-ulm.de \
    --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).