From: Andreas Schwab <schwab@linux-m68k.org>
To: Akash Hadke via Libc-alpha <libc-alpha@sourceware.org>
Cc: "Carlos O'Donell" <carlos@redhat.com>,
Akash Hadke <hadkeakash4@gmail.com>,
akash.hadke@kpit.com, aditya.tayade@kpit.com
Subject: Re: [PATCH] glibc: Apply patch for easy analysis of malloc issue
Date: Thu, 21 Jan 2021 09:40:57 +0100 [thread overview]
Message-ID: <87turau1gm.fsf@igel.home> (raw)
In-Reply-To: <CAK0fB4MXCyupSEZo0qOXXaJjqWQRr7LLrMOuABp3XLXPs0h4eQ@mail.gmail.com> (Akash Hadke via Libc-alpha's message of "Thu, 21 Jan 2021 11:08:47 +0530")
On Jan 21 2021, Akash Hadke via Libc-alpha wrote:
> Because valgrind didn't provide entire heap memory chunk and also it
> doesn't show illegally written values.
You can attach a debugger to inspect the failure.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
prev parent reply other threads:[~2021-01-21 8:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-20 15:42 Akash Hadke
2021-01-20 16:32 ` Carlos O'Donell
2021-01-21 5:38 ` Akash Hadke
2021-01-21 8:40 ` Andreas Schwab [this message]
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=87turau1gm.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=aditya.tayade@kpit.com \
--cc=akash.hadke@kpit.com \
--cc=carlos@redhat.com \
--cc=hadkeakash4@gmail.com \
--cc=libc-alpha@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).