public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/96997] [10/11 Regression] step over in gdb always stops in basic_string(const _CharT* __s, const _Alloc& __a = _Alloc())
Date: Tue, 16 Feb 2021 17:10:23 +0000	[thread overview]
Message-ID: <bug-96997-4-iCmCcJGqPC@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96997-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96997

--- Comment #8 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
The -fdump-tree-gimple-lineno changes between the previous revision and the
above one are:
--- pr96997.ii.005t.gimple_     2021-02-16 12:04:49.000000000 -0500
+++ pr96997.ii.005t.gimple      2021-02-16 12:05:28.000000000 -0500
@@ -6,12 +6,12 @@ main ()
   struct allocator D.36274;
   int D.39876;

-  [./example.cpp:7:27] std::allocator<char>::allocator ([./example.cpp:7:27]
&D.36232);
+  [./example.cpp:7:40] std::allocator<char>::allocator ([./example.cpp:7:40]
&D.36232);
   [./example.cpp:7:19] try
     {
       try
         {
-          [./example.cpp:7:27] std::__cxx11::basic_string<char>::basic_string
([./example.cpp:7:27] &D.36233, [./example.cpp:7:27] "str1", &D.36232);
+          [./example.cpp:7:40] std::__cxx11::basic_string<char>::basic_string
([./example.cpp:7:40] &D.36233, [./example.cpp:7:40] "str1",
[/opt/compiler-explorer/gcc-9.3.0/include/c++/9.3.0/bits/basic_string.h:525:59]
&D.36232);
           try
             {
               try
@@ -30,19 +30,19 @@ main ()
         }
       finally
         {
-          [./example.cpp:7:27] std::allocator<char>::~allocator
([./example.cpp:7:27] &D.36232);
+         
[/opt/compiler-explorer/gcc-9.3.0/include/c++/9.3.0/bits/basic_string.h:525:59]
std::allocator<char>::~allocator
([/opt/compiler-explorer/gcc-9.3.0/include/c++/9.3.0/bits/basic_string.h:525:59]
&D.36232);
         }
     }
   finally
     {
-      [./example.cpp:7:27] D.36232 = {CLOBBER};
+     
[/opt/compiler-explorer/gcc-9.3.0/include/c++/9.3.0/bits/basic_string.h:525:59]
D.36232 = {CLOBBER};
     }
twice (second time for example.cpp:8).

  parent reply	other threads:[~2021-02-16 17:10 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-09 12:29 [Bug debug/96997] New: " alexis.jeandet at member dot fsf.org
2020-09-09 15:47 ` [Bug debug/96997] " redi at gcc dot gnu.org
2020-09-10  7:29 ` [Bug debug/96997] [10/11 Regression] " rguenth at gcc dot gnu.org
2020-09-10  8:16 ` vries at gcc dot gnu.org
2020-09-10  8:19 ` vries at gcc dot gnu.org
2020-09-10  8:21 ` vries at gcc dot gnu.org
2020-09-10  9:29 ` rguenth at gcc dot gnu.org
2020-09-10 10:22 ` redi at gcc dot gnu.org
2021-02-16 17:01 ` jakub at gcc dot gnu.org
2021-02-16 17:10 ` jakub at gcc dot gnu.org [this message]
2021-02-16 17:29 ` jakub at gcc dot gnu.org
2021-02-16 18:11 ` ppalka at gcc dot gnu.org
2021-02-16 18:16 ` jakub at gcc dot gnu.org
2021-02-16 18:18 ` ppalka at gcc dot gnu.org
2021-02-17  1:49 ` cvs-commit at gcc dot gnu.org
2021-02-17 15:01 ` cvs-commit at gcc dot gnu.org
2021-02-23  3:12 ` ppalka at gcc dot gnu.org
2023-12-13 20:06 ` 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-96997-4-iCmCcJGqPC@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: 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).