From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug translator/6694] auto_free seems to trigger *** glibc detected *** stap: double free or corruption (fasttop)
Date: Mon, 30 Jun 2008 10:42:00 -0000 [thread overview]
Message-ID: <20080629184546.306.qmail@sourceware.org> (raw)
In-Reply-To: <20080625123602.6694.mwielaard@redhat.com>
------- Additional Comments From fche at redhat dot com 2008-06-29 18:45 -------
Tim, please work with Mark to find out whether there is some
reason to suspect Mark's build. If there is any doubt at all
in the auto_free code, please roll it back.
--
What |Removed |Added
----------------------------------------------------------------------------
CC|timoore at redhat dot com |fche at redhat dot com
AssignedTo|systemtap at sources dot |timoore at redhat dot com
|redhat dot com |
Status|NEW |ASSIGNED
http://sourceware.org/bugzilla/show_bug.cgi?id=6694
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
prev parent reply other threads:[~2008-06-29 18:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-25 19:28 [Bug translator/6694] New: " mwielaard at redhat dot com
2008-06-25 20:04 ` [Bug translator/6694] " fche at redhat dot com
2008-06-30 10:42 ` fche at redhat dot com [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=20080629184546.306.qmail@sourceware.org \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sources.redhat.com \
/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).