public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "amerey at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/29257] Double free of demangled symbol name
Date: Thu, 23 Jun 2022 16:43:05 +0000 [thread overview]
Message-ID: <bug-29257-4717-9yB5IMvEFX@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29257-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29257
Aaron Merey <amerey at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |amerey at redhat dot com
--- Comment #5 from Aaron Merey <amerey at redhat dot com> ---
Hi Magne, which version of elfutils are you using? I was only able to reproduce
this using an older package (elfutils-debuginfod-client-0.186-1.fc35.x86_64)
that uses 000-permission files to represent negative-cache-hits. When you used
touch to create the file it didn't have 000 permissions, so debuginfod returns
an empty file to gdb as if it's valid. Without manually adding the cache file
this situation should not occur.
More recent versions of debuginfod use empty files to represent
negative-cache-hits. In this case I can't reproduce the bug because debuginfod
correctly doesn't return the empty file to gdb.
(It looks like F36 contains an update version of elfutils-debuginfod-client but
F35 still provides an older 000-permisssion build, we should probably update
F35's elfutils-debuginfod-client.)
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-06-23 16:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-16 16:41 [Bug gdb/29257] New: " mhov at undo dot io
2022-06-16 18:07 ` [Bug gdb/29257] " mhov at undo dot io
2022-06-18 16:29 ` tromey at sourceware dot org
2022-06-23 13:53 ` mhov at undo dot io
2022-06-23 14:05 ` mhov at undo dot io
2022-06-23 16:43 ` amerey at redhat dot com [this message]
2022-06-24 16:16 ` mhov at undo dot io
2022-12-06 18:42 ` tromey at sourceware dot org
2022-12-06 19:01 ` tromey at sourceware dot org
2022-12-06 19:07 ` tromey at sourceware dot org
2022-12-07 20:55 ` amerey at redhat dot com
2022-12-09 17:55 ` mhov at undo dot io
2022-12-12 18:40 ` tromey at sourceware dot org
2023-04-13 17:46 ` tromey at sourceware dot org
2023-04-13 20:00 ` cvs-commit at gcc dot gnu.org
2023-04-13 20:00 ` tromey at sourceware dot 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-29257-4717-9yB5IMvEFX@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).