From: Paolo Bonzini <pbonzini@redhat.com>
To: Eduardo Otubo <otubo@redhat.com>, qemu-devel@nongnu.org
Cc: thuth@redhat.com, "qemu-trivial@nongnu.org" <qemu-trivial@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] fix qemu-system-unicore32 crashing when calling without -kernel
Date: Wed, 26 Jul 2017 17:28:09 +0200 [thread overview]
Message-ID: <4568463e-566f-538b-9be2-dae026670378@redhat.com> (raw)
In-Reply-To: <20170726150446.20381-1-otubo@redhat.com>
On 26/07/2017 17:04, Eduardo Otubo wrote:
> Starting qemu-system-unicore32 without the -kernel parameter results in
> an assert() returns false and aborts qemu. This patch replaces it with a
> proper error message followed by exit(1).
>
> Signed-off-by: Eduardo Otubo <otubo@redhat.com>
> ---
> hw/unicore32/puv3.c | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/hw/unicore32/puv3.c b/hw/unicore32/puv3.c
> index e9d1a60b6f..ff62efb4df 100644
> --- a/hw/unicore32/puv3.c
> +++ b/hw/unicore32/puv3.c
> @@ -92,7 +92,10 @@ static void puv3_load_kernel(const char *kernel_filename)
> if (kernel_filename == NULL && qtest_enabled()) {
> return;
> }
> - assert(kernel_filename != NULL);
> + if (kernel_filename == NULL) {
> + error_report("kernel parameter cannot be empty");
> + exit(1);
> + }
>
> /* only zImage format supported */
> size = load_image_targphys(kernel_filename, KERNEL_LOAD_ADDR,
>
Cc: qemu-trivial@nongnu.org
next prev parent reply other threads:[~2017-07-26 15:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-26 15:04 [Qemu-devel] [PATCH] fix qemu-system-unicore32 crashing when calling without -kernel Eduardo Otubo
2017-07-26 15:28 ` Paolo Bonzini [this message]
2017-07-26 15:28 ` Cleber Rosa
2017-07-26 15:38 ` Cleber Rosa
2017-07-26 15:52 ` Thomas Huth
2017-07-26 16:00 ` Philippe Mathieu-Daudé
2017-07-26 16:05 ` Thomas Huth
2017-07-26 16:50 ` Philippe Mathieu-Daudé
-- strict thread matches above, loose matches on Subject: below --
2017-07-28 11:53 Eduardo Otubo
2017-07-31 10:16 ` Michael Tokarev
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=4568463e-566f-538b-9be2-dae026670378@redhat.com \
--to=pbonzini@redhat.com \
--cc=otubo@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=thuth@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 NNTP newsgroup(s).