All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fam Zheng <famz@redhat.com>
To: Julio Faracco <jcfaracco@gmail.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Segmentation Fault running Raspberry Pi OS.
Date: Thu, 10 Nov 2016 10:28:12 +0800	[thread overview]
Message-ID: <20161110022812.GC8422@lemon> (raw)
In-Reply-To: <CAENf94+=MthC1CCBz1wCiW6iY3nfLpfQOHWGQJhfV7=y1HFQ4g@mail.gmail.com>

On Wed, 11/09 19:35, Julio Faracco wrote:
> Hi guys,
> 
> I was developing a simple OS for Raspberry Pi 2.
> When I was debugging my OS using "-s -S" options for QEMU, I was
> getting a segfault: Segmentation fault (core dumped).

Hello Julio,

What version of QEMU are you using? Please test with the current head of master
branch. If it crashes, could you try git bisect to find the bad commit?

I am not familiar with gdbstub/tlb code, so just giving some generic tips here.
My apology if they are too obvious.

Fam

  reply	other threads:[~2016-11-10  2:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-09 21:35 [Qemu-devel] Segmentation Fault running Raspberry Pi OS Julio Faracco
2016-11-10  2:28 ` Fam Zheng [this message]
2016-11-10  6:39 ` Stefan Weil
2016-11-11 22:23   ` Julio Faracco

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=20161110022812.GC8422@lemon \
    --to=famz@redhat.com \
    --cc=jcfaracco@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.