All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nathan Froyd <froydnj@codesourcery.com>
To: Taimoor Mirza <mooni_mirza@hotmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Inserting Memory Watch points
Date: Mon, 19 Apr 2010 06:06:25 -0700	[thread overview]
Message-ID: <20100419130625.GC18198@codesourcery.com> (raw)
In-Reply-To: <COL102-W729833CD17039A04D3ABD970B0@phx.gbl>

On Mon, Apr 19, 2010 at 12:11:46PM +0600, Taimoor Mirza wrote:
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread -1208740160 (LWP 1912)]
> gdb_set_stop_cpu (env=0x9ef36a0) at /usr/QEMU_Learning/QEMU_Src/qemu-0.12.3/gdbstub.c:2114
> 2114        gdbserver_state->c_cpu = env;
> (gdb) p env
> $1 = (struct CPUARMState *) 0x9ef36a0
> (gdb) p gdbserver_state->c_cpu
> Cannot access memory at address 0x0
> 
> Can anybody tell me whats wrong with this?

gdbserver_state is NULL.  You need to start QEMU with the -gdb switch
and connect to it via GDB for cpu_watchpoint_insert to work.

-Nathan

      reply	other threads:[~2010-04-19 13:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-19  6:11 [Qemu-devel] Inserting Memory Watch points Taimoor Mirza
2010-04-19 13:06 ` Nathan Froyd [this message]

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=20100419130625.GC18198@codesourcery.com \
    --to=froydnj@codesourcery.com \
    --cc=mooni_mirza@hotmail.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.