public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ondra at iuuk dot mff.cuni.cz" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug malloc/10345] malloc_printerr calls into malloc and then crashes again
Date: Tue, 28 May 2013 09:04:00 -0000 [thread overview]
Message-ID: <bug-10345-131-iUdyyVbmCW@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-10345-131@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=10345
OndrejBilka <ondra at iuuk dot mff.cuni.cz> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ondra at iuuk dot mff.cuni.cz
--- Comment #3 from OndrejBilka <ondra at iuuk dot mff.cuni.cz> ---
> This commit adds assert/fatal messages into the core file. So, reverting this
> means it will be missing in the core file, however messages printed by libc on
> stdout will continue to happen. Is this correct?
When looking to sysdeps/posix/libc_fatal.c there is no longer malloc present.
Running git blame shows it was changed in commit f8a3b5bf from 2011-05-15 which
is after Colin's message.
Did you tested with libc that contain commit f8a3b5bf ?
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2013-05-28 9:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-10345-131@http.sourceware.org/bugzilla/>
2012-02-21 1:51 ` jsm28 at gcc dot gnu.org
2012-02-24 18:31 ` andrew.beard at fidelissecurity dot com
2012-12-19 10:51 ` schwab@linux-m68k.org
2013-05-28 8:04 ` bharath.vegito at gmail dot com
2013-05-28 9:04 ` ondra at iuuk dot mff.cuni.cz [this message]
2013-05-28 17:17 ` bharath.vegito at gmail dot com
2013-10-14 13:58 ` neleai at seznam dot cz
2014-07-01 7:55 ` fweimer at redhat dot com
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-10345-131-iUdyyVbmCW@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).