From: Stefan Hajnoczi <stefanha@gmail.com>
To: Taimoor Mirza <taimoor.mrza@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Problems with QEMU sdcard while using glib 2.33.8
Date: Wed, 28 Aug 2013 15:38:07 +0200 [thread overview]
Message-ID: <20130828133807.GB12214@stefanha-thinkpad.muc.redhat.com> (raw)
In-Reply-To: <CAO6-N=bPZhGbH9rBfsY4sfwxn+oz8Fp-BngybzuAmC_x=GUyBg@mail.gmail.com>
On Wed, Aug 28, 2013 at 04:17:24PM +0500, Taimoor Mirza wrote:
> Thanks for your reply. Below are answers
>
> $ grep CONFIG_COROUTINE_BACKEND config-host.mak
> CONFIG_COROUTINE_BACKEND=win32
>
> (gdb) r
> Starting program: C:\tools\qemu\qemu-system-arm.exe
> -M realview-eb -m 256 -kernel Debug\\\\KD2.out -sd fat:16:rw:C:\\testCard
> [New Thread 3836.0x404]
> [New Thread 3836.0x87c]
> [New Thread 3836.0xd14]
> [New Thread 3836.0xc58]
> [Inferior 1 (process 3836) exited with code 03]
> (gdb) bt
> No stack.
It seems that gdb on Windows does not catch abort(3) - perhaps because
SIGABRT is not used (on Linux gdb will intercept SIGABRT and return to
the gdb prompt).
So you may need to set a breakpoint on abort(3) instead:
(gdb) b abort
(gdb) r
[...runs until abort(3) is called...]
(gdb) bt
next prev parent reply other threads:[~2013-08-28 13:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-28 5:14 [Qemu-devel] Problems with QEMU sdcard while using glib 2.33.8 Taimoor Mirza
2013-08-28 8:11 ` Stefan Hajnoczi
2013-08-28 11:17 ` Taimoor Mirza
2013-08-28 13:38 ` Stefan Hajnoczi [this message]
2013-08-28 19:10 ` Taimoor Mirza
2013-08-29 6:31 ` Taimoor Mirza
2013-08-29 6:59 ` Taimoor Mirza
2013-08-29 8:28 ` Stefan Hajnoczi
2013-09-05 11:02 ` Taimoor Mirza
2013-09-18 14:10 ` Stefan Hajnoczi
[not found] ` <CAO6-N=YYXGWE==E_jFB+onOCZQs=LQ5WxwUgiPSBH0vscgkPFw@mail.gmail.com>
2013-09-19 8:11 ` Stefan Hajnoczi
2013-09-19 13:38 ` Paolo Bonzini
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=20130828133807.GB12214@stefanha-thinkpad.muc.redhat.com \
--to=stefanha@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=taimoor.mrza@gmail.com \
/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).