public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/98419] wrong code when destructor of local variable modifies returned object
Date: Tue, 22 Dec 2020 12:36:16 +0000	[thread overview]
Message-ID: <bug-98419-4-GASL7lAMWA@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98419-4@http.gcc.gnu.org/bugzilla/>

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

Martin Liška <marxin at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |marxin at gcc dot gnu.org

--- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> ---
It seems you invoke a use-after-scope:

g++ pr98419.C -fsanitize=address,undefined && ./a.out 
=================================================================
==31013==ERROR: AddressSanitizer: stack-use-after-scope on address
0x7fffffffdf30 at pc 0x000000401532 bp 0x7fffffffdec0 sp 0x7fffffffdeb8
WRITE of size 4 at 0x7fffffffdf30 thread T0
    #0 0x401531 in B::~B() (/home/marxin/Programming/testcases/a.out+0x401531)
    #1 0x401293 in foo() (/home/marxin/Programming/testcases/a.out+0x401293)
    #2 0x4012fb in main (/home/marxin/Programming/testcases/a.out+0x4012fb)
    #3 0x7ffff676e151 in __libc_start_main (/lib64/libc.so.6+0x28151)
    #4 0x4010fd in _start (/home/marxin/Programming/testcases/a.out+0x4010fd)

Address 0x7fffffffdf30 is located in stack of thread T0 at offset 48 in frame
    #0 0x4011b5 in foo() (/home/marxin/Programming/testcases/a.out+0x4011b5)

  This frame has 2 object(s):
    [48, 52) '<unknown>' <== Memory access at offset 48 is inside this variable
    [64, 72) 'b' (line 17)
HINT: this may be a false positive if your program uses some custom stack
unwind mechanism, swapcontext or vfork
      (longjmp and C++ exceptions *are* supported)
SUMMARY: AddressSanitizer: stack-use-after-scope
(/home/marxin/Programming/testcases/a.out+0x401531) in B::~B()
Shadow bytes around the buggy address:
  0x10007fff7b90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  0x10007fff7ba0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  0x10007fff7bb0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  0x10007fff7bc0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  0x10007fff7bd0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
=>0x10007fff7be0: f1 f1 f1 f1 f1 f1[f8]f2 00 f3 f3 f3 00 00 00 00
  0x10007fff7bf0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  0x10007fff7c00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  0x10007fff7c10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  0x10007fff7c20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  0x10007fff7c30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Shadow byte legend (one shadow byte represents 8 application bytes):
  Addressable:           00
  Partially addressable: 01 02 03 04 05 06 07 
  Heap left redzone:       fa
  Freed heap region:       fd
  Stack left redzone:      f1
  Stack mid redzone:       f2
  Stack right redzone:     f3
  Stack after return:      f5
  Stack use after scope:   f8
  Global redzone:          f9
  Global init order:       f6
  Poisoned by user:        f7
  Container overflow:      fc
  Array cookie:            ac
  Intra object redzone:    bb
  ASan internal:           fe
  Left alloca redzone:     ca
  Right alloca redzone:    cb
  Shadow gap:              cc
==31013==ABORTING

  reply	other threads:[~2020-12-22 12:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-22 12:16 [Bug c++/98419] New: " leni536 at gmail dot com
2020-12-22 12:36 ` marxin at gcc dot gnu.org [this message]
2020-12-22 21:05 ` [Bug c++/98419] " leni536 at gmail dot com
2020-12-23 10:59 ` marxin 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-98419-4-GASL7lAMWA@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).