From: Filip Navara <filip.navara@gmail.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/2] Fix QCOW2 debugging code to compile with DEBUG_ALLOC defined.
Date: Tue, 23 Jun 2009 17:28:21 +0200 [thread overview]
Message-ID: <5b31733c0906230828i65949383k3f30d77dc342115f@mail.gmail.com> (raw)
In-Reply-To: <4A40EA58.6080600@redhat.com>
On Tue, Jun 23, 2009 at 4:44 PM, Kevin Wolf<kwolf@redhat.com> wrote:
> Filip Navara schrieb:
>> Signed-off-by: Filip Navara <filip.navara@gmail.com>
>> ---
>> block/qcow2.c | 2 +-
>> 1 files changed, 1 insertions(+), 1 deletions(-)
>>
>> diff --git a/block/qcow2.c b/block/qcow2.c
>> index 9acbddf..fdcd20b 100644
>> --- a/block/qcow2.c
>> +++ b/block/qcow2.c
>> @@ -251,7 +251,7 @@ static int qcow_open(BlockDriverState *bs, const char *filename, int flags)
>> goto fail;
>>
>> #ifdef DEBUG_ALLOC
>> - check_refcounts(bs);
>> + qcow2_check_refcounts(bs);
>> #endif
>> return 0;
>>
>
> Good point. However, this is not complete. During the qcow2 source split
> the #ifdefs have been spread over the files, but the #define hasn't
> moved to qcow2.h. To fix debugging you should move it there and fix the
> additional compile errors in the other files, too. Also, defining
> DEBUG_ALLOC2 gives even more errors, so maybe they should handled here
> as well.
>
> Kevin
I have sent a new patch that fixes all the QCOW2 debugging code in my
environment and moves the definitions to qcow2.h. Thanks for comments.
Best regards,
Filip Navara
prev parent reply other threads:[~2009-06-23 15:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-23 13:46 [Qemu-devel] [PATCH 1/2] Fix QCOW2 debugging code to compile with DEBUG_ALLOC defined Filip Navara
2009-06-23 14:44 ` Kevin Wolf
2009-06-23 15:28 ` Filip Navara [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=5b31733c0906230828i65949383k3f30d77dc342115f@mail.gmail.com \
--to=filip.navara@gmail.com \
--cc=kwolf@redhat.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).