All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: Laurent Desnogues <laurent.desnogues@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] tcg_abort()
Date: Wed, 16 Sep 2009 09:46:31 -0600	[thread overview]
Message-ID: <4AB10857.2030403@mlbassoc.com> (raw)
In-Reply-To: <761ea48b0909160831p3201956u79077c802e6c349a@mail.gmail.com>

On 09/16/2009 09:31 AM, Laurent Desnogues wrote:
> On Wed, Sep 16, 2009 at 5:19 PM, Gary Thomas<gary@mlbassoc.com>  wrote:
>> I've run into some of these in arm/tcg-target.c
>>
>> Can someone explain why they are there and how I can get past them?
>
> Not if you don't provide more information such as:
>
>    - QEMU version

Today's version from GIT

>    - abort line

/qemu-git-2009_09_16/tcg/arm/tcg-target.c:773: tcg fatal error

>    - how to reproduce the issue

This one's harder - I'm running an x86 gnome application on an ARM
system.  I'm not sure exactly what it was doing when the abort happened.

Questions:
   * The function in tcp-target.c seems complete, but it has
       #if 1
         tcg_abort();
       #endif
     which implies it's not complete or maybe just untested?
   * How can I gather more information about what was going on
     at the time to aid in fixing this?

Thanks


-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

  reply	other threads:[~2009-09-16 15:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-16 15:19 [Qemu-devel] tcg_abort() Gary Thomas
2009-09-16 15:31 ` Laurent Desnogues
2009-09-16 15:46   ` Gary Thomas [this message]
2009-09-16 16:16     ` Laurent Desnogues
2009-09-16 18:22       ` Gary Thomas
2009-09-16 18:24         ` Laurent Desnogues
2009-09-25 22:48       ` Laurent Desnogues
2009-09-28 11:15         ` Paul Brook
2009-09-28 11:24           ` Laurent Desnogues

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=4AB10857.2030403@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=laurent.desnogues@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 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.