From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Crosthwaite <peter.crosthwaite@xilinx.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Peter Cheung <mcheung63@hotmail.com>
Subject: Re: [Qemu-devel] latest qemu with gdb remote not working
Date: Mon, 03 Jun 2013 09:47:41 +0200 [thread overview]
Message-ID: <51AC4A1D.20105@redhat.com> (raw)
In-Reply-To: <CAEgOgz5CTgzb+iBHkhpos78L3L_FYCCEVchDdxPCbU72r3S7xA@mail.gmail.com>
Il 03/06/2013 09:42, Peter Crosthwaite ha scritto:
> Hi Peter and Peter :)
>
> On Sun, Jun 2, 2013 at 7:27 PM, Peter Maydell <peter.maydell@linaro.org> wrote:
>> On 2 June 2013 06:46, Peter Cheung <mcheung63@hotmail.com> wrote:
>>> I just tried to compile the latest qemu on Fedora 18 64 bits,
>>> it is also fail. When i press "c" in gdb, the qemu won't start
>>> running.
>>
>> Good. This significantly increases the chances that somebody
>> will investigate.
>
> I think I may have replicated as well. qemu-system-arm on Ubuntu 10.04 host.
> And it works again for me after a revert of:
>
> commit 87f25c12bfeaaa0c41fb857713bbc7e8a9b757dc
> Author: Paolo Bonzini <pbonzini@redhat.com>
> Date: Thu May 30 13:20:40 2013 +0200
>
> gdbstub: do not restart crashed guest
>
> If a guest has crashed with an internal error or similar, detaching
> gdb (or any other debugger action) should not restart it.
>
> Cc: Jan Kiszka <jan.kiszka@siemens.com>
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> Reviewed-by: Laszlo Ersek <lersek@redhat.com>
> Message-id: 1369912840-18577-1-git-send-email-pbonzini@redhat.com
> Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
Oops, indeed you need to type cont in both gdb and the monitor after
this patch. Funny I didn't notice; the fix should be to use
!runstate_needs_reset() instead of runstate_check(RUN_STATE_DEBUG).
But it is likely a different bug than the Mac OS X one.
Paolo
> Ill dig further before sending through minimal replication
> instructions (gotta run!)
> but Peter Cheung, can you please try your test case after reverting this commit,
> to see if its perhaps the same bug?
>
> $ git revert 87f25c12bfeaaa0c41fb857713bbc7e8a9b757dc
>
> Regards,
> Peter
>
>>
>>> But one thing fedora is different than mac, when i connect gdb to qemu, it
>>> won't say "warning: Error 268435459 getting port names from mach_port_names"
>>
>> That looks like a Mac GDB specific issue.
>>
>>> In my mac, i use gcc from mac port, here is the version detail:
>>>
>>> /Users/peter>gcc -v
>>
>>> gcc version 4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2336.1.00)
>>
>> This is pretty ancient -- I'd suggest using clang to build
>> QEMU instead. (It probably won't fix your problem here, though.)
>>
>> What command line are you using to configure and build QEMU?
>>
>> thanks
>> -- PMM
>>
next prev parent reply other threads:[~2013-06-03 7:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-01 20:09 [Qemu-devel] latest qemu with gdb remote not working Peter Cheung
2013-06-01 22:57 ` Peter Crosthwaite
2013-06-01 23:09 ` Peter Maydell
2013-06-02 5:46 ` Peter Cheung
2013-06-02 9:27 ` Peter Maydell
2013-06-03 7:42 ` Peter Crosthwaite
2013-06-03 7:47 ` Paolo Bonzini [this message]
2013-06-10 15:16 ` Peter Cheung
2013-06-02 5:05 ` Peter Cheung
2013-06-03 12:19 ` Eric Blake
2013-06-10 15:14 ` 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=51AC4A1D.20105@redhat.com \
--to=pbonzini@redhat.com \
--cc=mcheung63@hotmail.com \
--cc=peter.crosthwaite@xilinx.com \
--cc=peter.maydell@linaro.org \
--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.