public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hadkeakash4 at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/27216] New: Illegally written memory chunk address and its value is not getting printed in core file
Date: Wed, 20 Jan 2021 15:08:44 +0000 [thread overview]
Message-ID: <bug-27216-131@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=27216
Bug ID: 27216
Summary: Illegally written memory chunk address and its value
is not getting printed in core file
Product: glibc
Version: 2.27
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: libc
Assignee: unassigned at sourceware dot org
Reporter: hadkeakash4 at gmail dot com
CC: drepper.fsp at gmail dot com
Target Milestone: ---
When illegal memory write operation (write after free) get performed and code
fails it should provide address of illegally written memory chunk and its value
in core file for debugging purpose.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2021-01-20 15:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-20 15:08 hadkeakash4 at gmail dot com [this message]
2021-01-20 15:16 ` [Bug libc/27216] " carlos at redhat dot com
2021-01-20 15:38 ` schwab@linux-m68k.org
2021-01-21 13:28 ` hadkeakash4 at gmail dot com
2021-01-21 13:48 ` carlos at redhat dot com
2021-01-21 14:20 ` schwab@linux-m68k.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-27216-131@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@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).