From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Tweedie Subject: Re: No CONFIG_DEBUG_INFO on x86_64 Xen; why not? Date: Thu, 6 Apr 2006 21:57:36 -0400 Message-ID: <20060407015736.GC629@devserv.devel.redhat.com> References: <1144282621.3447.5.camel@orbit.scot.redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: xen-devel List-Id: xen-devel@lists.xenproject.org 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