From: Markus Armbruster <armbru@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: qemu-devel@nongnu.org, Kevin Wolf <kwolf@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
qemu-block@nongnu.org, Eric Blake <eblake@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v6 01/10] qom: add helpers for UserCreatable object types
Date: Wed, 27 Apr 2016 15:37:21 +0200 [thread overview]
Message-ID: <87k2jjfa0e.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <8737q7ierk.fsf@dusky.pond.sub.org> (Markus Armbruster's message of "Wed, 27 Apr 2016 11:26:23 +0200")
Markus Armbruster <armbru@redhat.com> writes:
> This commit regresses error message quality from
>
> $ qemu-system-x86_64 -nodefaults -display none -object secret,id=sec0,data=letmein,format=raw,foo=bar
> qemu-system-x86_64: -object secret,id=sec0,data=letmein,format=raw,foo=bar: Property '.foo' not found
>
> to just
>
> qemu-system-x86_64: Property '.foo' not found
>
> Clue: cur_loc points to garbage.
>
> (gdb) p cur_loc
> $1 = (Location *) 0x7fffffffdc10
> (gdb) p *cur_loc
> $2 = {kind = (unknown: 4294958128), num = 32767,
> ptr = 0x555555b804a2 <error_report_err+44>, prev = 0x5555565d2770 <std_loc>}
>
> Looks like cur_loc is dangling. Happens when you forget to loc_pop() a
> Location before it dies. This one is on the stack.
>
> *Might* be release critical.
>
> For comparison, this is how it looks before the patch:
>
> (gdb) p cur_loc
> $1 = (Location *) 0x7fffffffdc10
> (gdb) p *cur_loc
> $2 = {kind = LOC_CMDLINE, num = 2, ptr = 0x7fffffffe018, prev =
> 0x5555565d2770 <std_loc>}
>
> Reported-by: Eric Blake <eblake@redhat.com>
I think I nailed it. Preparing patches...
next prev parent reply other threads:[~2016-04-27 13:37 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-15 14:33 [Qemu-devel] [PATCH v6 00/10] Make qemu-img/qemu-nbd/qemu-io CLI more flexible Daniel P. Berrange
2016-02-15 14:33 ` [Qemu-devel] [PATCH v6 01/10] qom: add helpers for UserCreatable object types Daniel P. Berrange
2016-04-27 9:26 ` Markus Armbruster
2016-04-27 9:58 ` Daniel P. Berrange
2016-04-27 12:43 ` Eric Blake
2016-04-27 14:55 ` Daniel P. Berrange
2016-04-27 13:37 ` Markus Armbruster [this message]
2016-02-15 14:33 ` [Qemu-devel] [PATCH v6 02/10] qemu-io: add support for --object command line arg Daniel P. Berrange
2016-02-15 14:33 ` [Qemu-devel] [PATCH v6 03/10] qemu-nbd: " Daniel P. Berrange
2016-02-15 14:33 ` [Qemu-devel] [PATCH v6 04/10] qemu-img: " Daniel P. Berrange
2016-02-15 14:33 ` [Qemu-devel] [PATCH v6 05/10] qemu-io: allow specifying image as a set of options args Daniel P. Berrange
2016-02-15 14:33 ` [Qemu-devel] [PATCH v6 06/10] qemu-nbd: " Daniel P. Berrange
2016-02-15 14:33 ` [Qemu-devel] [PATCH v6 07/10] qemu-img: " Daniel P. Berrange
2016-02-15 14:33 ` [Qemu-devel] [PATCH v6 08/10] qemu-nbd: don't overlap long option values with short options Daniel P. Berrange
2016-02-15 14:33 ` [Qemu-devel] [PATCH v6 09/10] qemu-nbd: use no_argument/required_argument constants Daniel P. Berrange
2016-02-15 14:33 ` [Qemu-devel] [PATCH v6 10/10] qemu-io: " Daniel P. Berrange
2016-02-15 15:53 ` [Qemu-devel] [PATCH v6 00/10] Make qemu-img/qemu-nbd/qemu-io CLI more flexible Kevin Wolf
2016-02-17 10:10 ` Daniel P. Berrange
2016-02-17 10:37 ` Kevin Wolf
2016-02-17 10:41 ` Daniel P. Berrange
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=87k2jjfa0e.fsf@dusky.pond.sub.org \
--to=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=eblake@redhat.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.