From: Stephen Tweedie <sct@redhat.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: No CONFIG_DEBUG_INFO on x86_64 Xen; why not?
Date: Thu, 6 Apr 2006 21:57:36 -0400 [thread overview]
Message-ID: <20060407015736.GC629@devserv.devel.redhat.com> (raw)
In-Reply-To: <a1b01ac4d39c4986f87ecc1b869a5781@cl.cam.ac.uk>
Hi,
On Thu, Apr 06, 2006 at 09:51:06AM +0100, Keir Fraser wrote:
> >Anyone remember, or object to reenabling CONFIG_DEBUG_INFO?
>
> Well, it builds and boots fine, and we leave it disabled by default
> anyway, so I'll remove our patch to Kconfig.debug. I think maybe there
> was a problem with our port of debug code in entry-xen.S, but I see
> that file forcibly disables CONFIG_DEBUG_INFO when it builds, which is
> probably the better 'fix' for the time being.
Right, entry-xen.S has problems --- it's broken even with the
CONFIG_DEBUG_INFO disable, as setting the new CONFIG_UNWIND_INFO
option still breaks it again. But that's just as easy to disable as a
temporary workaround. (I'd still like to find out why CFI is breaking
on Xen with those options disabled, though.)
--Stephen
prev parent reply other threads:[~2006-04-07 1:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-06 0:17 No CONFIG_DEBUG_INFO on x86_64 Xen; why not? Stephen C. Tweedie
2006-04-06 8:51 ` Keir Fraser
2006-04-07 1:57 ` Stephen Tweedie [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=20060407015736.GC629@devserv.devel.redhat.com \
--to=sct@redhat.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--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.