qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Lionel Landwerlin <lionel.landwerlin@openwide.fr>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] User emulation & gdb & sigsegv
Date: Thu, 11 Dec 2008 00:06:53 +0100	[thread overview]
Message-ID: <1228950413.3898.6.camel@cocoduo.atr> (raw)

Hello,

Currently, when using gdb connected to qemu, if a sigsegv is raised,
Qemu just exits.

How should I modify Qemu to redirect this last signal to the connected
gdb and print a stack trace at least ?

I tried to call gdb_handlesig(gdbstub.c) from
force_sig(linux-user/signal.c) but Qemu just crashes.

Any idea is welcome :)

Regards,

-- 
Lione Landwerlin                                         

O p e n W i d e                    14, rue Gaillon 75002 Paris

             reply	other threads:[~2008-12-10 23:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-10 23:06 Lionel Landwerlin [this message]
2008-12-10 23:18 ` [Qemu-devel] User emulation & gdb & sigsegv Edgar E. Iglesias
2008-12-11 21:42   ` Lionel Landwerlin
2008-12-12  8:44     ` Edgar E. Iglesias
2008-12-17 19:45 ` Daniel Jacobowitz

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=1228950413.3898.6.camel@cocoduo.atr \
    --to=lionel.landwerlin@openwide.fr \
    --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).