public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Mark Mitchell <mark@codesourcery.com> 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: Fri, 21 Feb 2003 17:06:00 -0000 [thread overview] Message-ID: <20030221170600.30153.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/4966; it has been noted by GNATS. From: Mark Mitchell <mark@codesourcery.com> To: Matthias Meixner <meixner@dvs1.informatik.tu-darmstadt.de>, "mmitchel@gcc.gnu.org" <mmitchel@gcc.gnu.org>, "gcc-bugs@gcc.gnu.org" <gcc-bugs@gcc.gnu.org>, "gcc-prs@gcc.gnu.org" <gcc-prs@gcc.gnu.org>, "meixner@rbg.informatik.tu-darmstadt.de" <meixner@rbg.informatik.tu-darmstadt.de>, "nobody@gcc.gnu.org" <nobody@gcc.gnu.org>, "rodrigc@gcc.gnu.org" <rodrigc@gcc.gnu.org>, "gcc-gnats@gcc.gnu.org" <gcc-gnats@gcc.gnu.org> Cc: Subject: Re: c++/4966: [3.2/3.3/3.4 regression] g++ generates incorrect debugging information Date: Fri, 21 Feb 2003 08:56:00 -0800 --On Friday, February 21, 2003 09:29:12 AM +0100 Matthias Meixner <meixner@dvs1.informatik.tu-darmstadt.de> wrote: > Hi! > > mmitchel@gcc.gnu.org wrote: >> Synopsis: [3.2/3.3/3.4 regression] g++ generates incorrect debugging >> information >> >> State-Changed-From-To: analyzed->closed >> State-Changed-By: mmitchel >> State-Changed-When: Fri Feb 21 02:25:27 2003 >> State-Changed-Why: >> Not a defect. >> >> http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=g >> cc&pr=4966 > > Did you forward that to the maintainers of gdb? No -- but I will if you tell me how best to do that. Thanks, -- Mark Mitchell mark@codesourcery.com CodeSourcery, LLC http://www.codesourcery.com
next reply other threads:[~2003-02-21 17:06 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-02-21 17:06 Mark Mitchell [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-02-21 14:56 Matthias Meixner 2003-02-21 2:25 mmitchel 2003-01-11 1:46 Christian Ehrhardt 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=20030221170600.30153.qmail@sources.redhat.com \ --to=mark@codesourcery.com \ --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: linkBe 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).