From: Frederic Konrad <fred.konrad@greensocs.com>
To: Peter Cheung <mcheung63@hotmail.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] qemu-1.5.0 gdb not working
Date: Sat, 15 Jun 2013 20:56:57 +0200 [thread overview]
Message-ID: <51BCB8F9.3090301@greensocs.com> (raw)
In-Reply-To: <BAY177-W230297FBCE619F47ADF407B5810@phx.gbl>
[-- Attachment #1: Type: text/plain, Size: 1127 bytes --]
On 15/06/2013 20:37, Peter Cheung wrote:
> qemu-1.5.0 gdb not working
>
> In mac OSX, compile by :
> ./configure --cc=/opt/local/bin/gcc-mp-4.8 --enable-cocoa
> --target-list=x86_64-softmmu --audio-drv-list=coreaudio
> --prefix=/Users/peter/qemu --enable-debug --disable-werror
> --extra-cflags=-O2 --enable-vnc
>
> start qemu by:
> ~/qemu/bin/qemu-system-x86_64 -hda hd10meg.img -gdb tcp::1234 -k en-us
> -S -m 256m
>
> i start gdb and insert two breakpoints at 0x7c00 and 0x7c01, after
> "c", it hit 0x7c00. Then i "c" again, it stay in 0x7c00, but it should
> execute 0x7c01.
>
> [New thread 1]
> warning: Error 268435459 getting port names from mach_port_names
> [Switching to process 1 thread 0x0]
> 0x0000fff0 in ?? ()
> Breakpoint 1 at 0x7c00
> Breakpoint 2 at 0x7c01
> (gdb) c
> Continuing.
>
> Breakpoint 1, 0x00007c00 in ?? ()
> (gdb) c
> Continuing.
Hi,
What if you type stepi?
>
> Breakpoint 1, 0x00007c00 in ?? ()
> (gdb) c
> Continuing.
>
> Breakpoint 1, 0x00007c00 in ?? ()
> (gdb) c
> Continuing.
>
> Breakpoint 1, 0x00007c00 in ?? ()
> (gdb) c
> Continuing.
>
> Breakpoint 1, 0x00007c00 in ?? ()
> (gdb)
>
>
[-- Attachment #2: Type: text/html, Size: 2764 bytes --]
next prev parent reply other threads:[~2013-06-15 18:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-15 18:37 [Qemu-devel] qemu-1.5.0 gdb not working Peter Cheung
2013-06-15 18:56 ` Frederic Konrad [this message]
2013-06-15 23:55 ` Peter Cheung
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=51BCB8F9.3090301@greensocs.com \
--to=fred.konrad@greensocs.com \
--cc=mcheung63@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 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).