public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "asmwarrior at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/49951] [4.5/4.6/4.7 Regression] Debug stepping behavior regarding g++ Class destructor has changed for the worse starting at gcc 4.5.0 Date: Tue, 03 Feb 2015 01:04:00 -0000 [thread overview] Message-ID: <bug-49951-4-cuNW08CnW5@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-49951-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49951 --- Comment #21 from asmwarrior <asmwarrior at gmail dot com> --- I just test the sample code in comment 20 with GCC 4.9.2, and I see this "jumpy" behaviour still exists, do we need to reopen this bug? Thanks.
next prev parent reply other threads:[~2015-02-03 1:04 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-08-02 20:07 [Bug debug/49951] New: " peter.thompson at roguewave dot com 2011-08-02 20:15 ` [Bug debug/49951] " peter.thompson at roguewave dot com 2011-08-03 9:35 ` [Bug debug/49951] [4.5/4.6/4.7 Regression] " rguenth at gcc dot gnu.org 2011-08-04 8:45 ` jakub at gcc dot gnu.org 2011-10-10 12:07 ` rguenth at gcc dot gnu.org 2011-10-27 10:02 ` rguenth at gcc dot gnu.org 2011-10-29 14:07 ` asmwarrior at gmail dot com 2011-11-29 19:44 ` redi at gcc dot gnu.org 2011-11-29 23:07 ` manu at gcc dot gnu.org 2011-12-02 10:48 ` dodji at gcc dot gnu.org 2011-12-03 18:25 ` dodji at gcc dot gnu.org 2011-12-03 19:04 ` manu at gcc dot gnu.org 2011-12-03 20:57 ` dodji at seketeli dot org 2011-12-20 13:41 ` dodji at gcc dot gnu.org 2011-12-20 13:43 ` dodji at gcc dot gnu.org 2011-12-20 14:16 ` redi at gcc dot gnu.org 2011-12-21 3:44 ` asmwarrior at gmail dot com 2012-01-02 12:03 ` dodji at seketeli dot org 2012-01-02 17:12 ` dodji at gcc dot gnu.org 2012-12-22 4:00 ` pinskia at gcc dot gnu.org 2013-10-28 7:56 ` asmwarrior at gmail dot com 2013-10-28 13:15 ` asmwarrior at gmail dot com 2015-02-03 1:04 ` asmwarrior at gmail dot com [this message] 2021-04-14 0:20 ` cvs-commit at gcc dot gnu.org
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=bug-49951-4-cuNW08CnW5@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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).