All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Liviu Ionescu <ilg@livius.net>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] segmentation fault in object.c:type_initialize_interface() if interface not defined
Date: Sun, 3 Apr 2016 17:43:11 +0100	[thread overview]
Message-ID: <CAFEAcA-MxcR3_j-nQyA5Fy9Dyhak0rOtZHsnq6mLCfyiug++0Q@mail.gmail.com> (raw)
In-Reply-To: <B682BEE2-49CA-4C74-A3A6-FFCB7E662CF0@livius.net>

On 3 April 2016 at 16:40, Liviu Ionescu <ilg@livius.net> wrote:
>
>> On 03 Apr 2016, at 15:28, Peter Maydell <peter.maydell@linaro.org> wrote:
>
>> since hw/arm/boot.o is in obj-y it should always be built,
>
> not necessarily, in my build configuration I have if's that
> exclude most of the files non related to Cortex-M.

boot.o is in obj-y; it is (I think) impossible to
build a v7M supporting QEMU without boot.o unless you've modified
the makefiles for some reason. That would not be a configuration
issue or a bug in QEMU, but a problem with your local modifications.

> in previous versions boot.o was not needed. in 2.5.1 you
> introduced a non-obvious dependency to it and the build
> passed, but the program crashed.
>
>> but we could assert on it rather than just crashing.
>
> my suggestion is to assert, it is easier to debug a failed
> assertion.

Yes, I agree.

thanks
-- PMM

  reply	other threads:[~2016-04-03 16:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-02 22:15 [Qemu-devel] segmentation fault in object.c:type_initialize_interface() if interface not defined Liviu Ionescu
2016-04-03 12:28 ` Peter Maydell
2016-04-03 15:40   ` Liviu Ionescu
2016-04-03 16:43     ` Peter Maydell [this message]
2016-04-03 16:57       ` Liviu Ionescu
2016-04-03 17:01         ` Peter Maydell
2016-04-03 17:56           ` Liviu Ionescu
2016-04-03 21:30             ` Peter Maydell
2016-04-03 21:42               ` Liviu Ionescu
2016-04-03 21:59                 ` Peter Maydell

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=CAFEAcA-MxcR3_j-nQyA5Fy9Dyhak0rOtZHsnq6mLCfyiug++0Q@mail.gmail.com \
    --to=peter.maydell@linaro.org \
    --cc=ilg@livius.net \
    --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.