From: Rik van Riel <riel@redhat.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com, jun.nakajima@intel.com
Subject: Re: BUG: x86-64 VT crash backtrace
Date: Tue, 25 Jul 2006 14:42:04 -0400 [thread overview]
Message-ID: <44C665FC.4080702@redhat.com> (raw)
In-Reply-To: <3decfd6f4148bb14adb9e7cf3dfca634@cl.cam.ac.uk>
[-- Attachment #1: Type: text/plain, Size: 534 bytes --]
Keir Fraser wrote:
> But you're running a debug build, so you have a 4kB stack.
That seems wrong. The debug build enables extra code, so if anything
it would need more stack space than the standard build. Simply running
the extra code in the same stack space should be enough...
Does the attached patch look remotely sane?
--
"Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it." - Brian W. Kernighan
[-- Attachment #2: stackstack --]
[-- Type: text/plain, Size: 325 bytes --]
--- ./xen/include/asm-x86/config.h.stackstack 2006-07-25 14:38:28.000000000 -0400
+++ ./xen/include/asm-x86/config.h 2006-07-25 14:38:31.000000000 -0400
@@ -67,10 +67,10 @@
#ifndef NDEBUG
#define MEMORY_GUARD
+#endif
#ifdef __x86_64__
#define STACK_ORDER 2
#endif
-#endif
#ifndef STACK_ORDER
#define STACK_ORDER 1
[-- Attachment #3: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
prev parent reply other threads:[~2006-07-25 18:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-25 16:02 BUG: x86-64 VT crash backtrace Rik van Riel
2006-07-25 16:55 ` Rik van Riel
2006-07-25 17:12 ` Keir Fraser
2006-07-25 16:57 ` Keir Fraser
2006-07-25 17:09 ` Rik van Riel
2006-07-25 17:15 ` Keir Fraser
2006-07-25 18:42 ` Rik van Riel [this message]
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=44C665FC.4080702@redhat.com \
--to=riel@redhat.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=jun.nakajima@intel.com \
--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.