public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: dberlin@sources.redhat.com To: dberlin@sources.redhat.com, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, schmid@snake.iap.physik.tu-darmstadt.de Subject: Re: debug/1819: severe problems debugging c++-code (libstdc++) Date: Mon, 11 Jun 2001 10:30:00 -0000 [thread overview] Message-ID: <20010611173022.28450.qmail@sourceware.cygnus.com> (raw) Synopsis: severe problems debugging c++-code (libstdc++) Responsible-Changed-From-To: unassigned->dberlin Responsible-Changed-By: dberlin Responsible-Changed-When: Mon Jun 11 10:30:21 2001 Responsible-Changed-Why: Mine State-Changed-From-To: open->closed State-Changed-By: dberlin State-Changed-When: Mon Jun 11 10:30:21 2001 State-Changed-Why: This is a combination of a gdb problem, and a bug that is already fixed (the line number problem). The gdb problem will be fixed in gdb cvs very soon now. Since the gcc portion of the bug has been fixed, i've closed this CR http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=1819&database=gcc
next reply other threads:[~2001-06-11 10:30 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-06-11 10:30 dberlin [this message] -- strict thread matches above, loose matches on Subject: below -- 2001-04-01 0:00 Phil Edwards
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=20010611173022.28450.qmail@sourceware.cygnus.com \ --to=dberlin@sources.redhat.com \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@gcc.gnu.org \ --cc=schmid@snake.iap.physik.tu-darmstadt.de \ /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).