From: Blue Swirl <blauwirbel@gmail.com>
To: qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: [PATCH] [RFC] qemu_malloc dynamic checking v2
Date: Thu, 16 Apr 2009 21:23:23 +0300 [thread overview]
Message-ID: <f43fc5580904161123k1b5b43cfqc21e1331a748006a@mail.gmail.com> (raw)
In-Reply-To: <f43fc5580904161049o2ea7b94mc7a14ba78f76f64b@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 475 bytes --]
On 4/16/09, Blue Swirl <blauwirbel@gmail.com> wrote:
> Hi,
>
> This version adds stricter checking for also normal
> malloc/free/memalign functions.
>
> Actually the crashes with the previous version were caused by bugs in
> the checker itself instead of function mismatch. With this version,
> also i386 works.
>
> I'm not so sure this approach is effective, I found more mismatches
> with simple grep. Committing it would not hurt though.
This time with the patch.
[-- Attachment #2: qemu_malloc_debug.diff --]
[-- Type: plain/text, Size: 5194 bytes --]
prev parent reply other threads:[~2009-04-16 18:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-16 17:49 [Qemu-devel] [PATCH] [RFC] qemu_malloc dynamic checking v2 Blue Swirl
2009-04-16 18:23 ` Blue Swirl [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=f43fc5580904161123k1b5b43cfqc21e1331a748006a@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=qemu-devel@nongnu.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 NNTP newsgroup(s).