public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/31258] [gdb] ThreadSanitizer: heap-use-after-free in memmove
Date: Thu, 18 Jan 2024 14:27:39 +0000	[thread overview]
Message-ID: <bug-31258-4717-N5sO5bbGrD@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31258-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=31258

--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #0)
> When building gdb with O0 -fsanitize=thread, and run test-case
> gdb.ada/uninitialized_vars.exp, I run into a heap-user-after-free:
> (gdb) info locals
> a = 0
> z = (a => 1, b => false, c => 2.0)
> y = (a => 184, c => 9.18340949e-41, d => -411009023)

This was with f39 aarch64, using gcc 13.

Also reproduced on openSUSE Tumbleweed x86_64, likewise using gcc 13.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  reply	other threads:[~2024-01-18 14:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-18  9:07 [Bug gdb/31258] New: " vries at gcc dot gnu.org
2024-01-18 14:27 ` vries at gcc dot gnu.org [this message]
2024-01-18 16:44 ` [Bug gdb/31258] " vries at gcc dot gnu.org
2024-01-19 15:39 ` vries at gcc dot gnu.org
2024-01-20 23:20 ` vries at gcc dot gnu.org
2024-01-21  9:08 ` [Bug exp/31258] " vries at gcc dot gnu.org
2024-01-22 13:27 ` vries at gcc dot gnu.org
2024-02-19  8:59 ` cvs-commit at gcc dot gnu.org
2024-02-19  9:01 ` vries 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-31258-4717-N5sO5bbGrD@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.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).