qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Mulyadi Santosa <mulyadi.santosa@gmail.com>
To: Jacques <Jacques@rambo-mes.net>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu gdb issue
Date: Fri, 16 Mar 2012 00:13:04 +0700	[thread overview]
Message-ID: <CAGdaadbShhtHP0r351b2sO2HWmFCHG7nPpxW__HB3xQEZa+_dg@mail.gmail.com> (raw)
In-Reply-To: <4F6212C2.4030104@rambo-mes.net>

Hi...

On Thu, Mar 15, 2012 at 23:03, Jacques <Jacques@rambo-mes.net> wrote:
> I'm running an application in qemu through the userspace qemu-i386 and
> attaching to the process with gdb. I have pygdb scripts that then
> interact with gdb.
>
> The issue is that at some point I want to change $eip and redirect
> instruction flow. I then set $eip to the value I need which gives me the
> following:
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x46367046 in ?? ()

I am not keen in this kind of situation,but I think you hit "non
existing" EIP. By that, I mean  maybe you think such EIP truly exist
(based on ELF info perhaps?), but in reality since qemu user mode do
dynamic translations and not really following ELF offset, you got
segfault.


-- 
regards,

Mulyadi Santosa
Freelance Linux trainer and consultant

blog: the-hydra.blogspot.com
training: mulyaditraining.blogspot.com

  reply	other threads:[~2012-03-15 17:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-15 16:03 [Qemu-devel] qemu gdb issue Jacques
2012-03-15 17:13 ` Mulyadi Santosa [this message]
2012-03-16  7:13   ` Jacques
2012-03-16 19:10     ` Mulyadi Santosa
2012-03-16 19:23       ` 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=CAGdaadbShhtHP0r351b2sO2HWmFCHG7nPpxW__HB3xQEZa+_dg@mail.gmail.com \
    --to=mulyadi.santosa@gmail.com \
    --cc=Jacques@rambo-mes.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 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).