All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerd Knorr <kraxel@bytesex.org>
To: xen-devel@lists.xensource.com
Subject: double fault ...
Date: Mon, 2 May 2005 16:51:44 +0200	[thread overview]
Message-ID: <20050502145143.GB15699@bytesex> (raw)

... happens with panics when compiled with debugging.
panic() calls debugger_trap_immediate(), which triggers
do_int3, which calls panic(), which recurses until the
stack is full => bang!

cheers,

  Gerd

-- 
#define printk(args...) fprintf(stderr, ## args)

             reply	other threads:[~2005-05-02 14:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-02 14:51 Gerd Knorr [this message]
2005-05-02 15:23 ` double fault Keir Fraser
2005-05-02 15:53   ` Gerd Knorr
2005-05-02 16:02     ` Kip Macy
2005-05-02 16:07     ` Keir Fraser
2005-05-02 16:18       ` Gerd Knorr

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=20050502145143.GB15699@bytesex \
    --to=kraxel@bytesex.org \
    --cc=xen-devel@lists.xensource.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 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.