All of lore.kernel.org
 help / color / mirror / Atom feed
* No CONFIG_DEBUG_INFO on x86_64 Xen; why not?
@ 2006-04-06  0:17 Stephen C. Tweedie
  2006-04-06  8:51 ` Keir Fraser
  0 siblings, 1 reply; 3+ messages in thread
From: Stephen C. Tweedie @ 2006-04-06  0:17 UTC (permalink / raw)
  To: xen-devel

Hi all,

lib/Kconfig.debug contains:

config DEBUG_INFO
        bool "Compile the kernel with debug info"
        depends on DEBUG_KERNEL && !X86_64_XEN

Does anyone recall why this was disabled for X86_64_XEN?  

hg annotate xen-unstable.hg leads to the cset description

        Update linux sparse tree to subarch layout.

and linux-2.6-merge.hg shows 

        various fixup in Kconfig to handle Xen
        
neither of which are particularly helpful.  I've just completed a build
with this change reverted and -g enabled and it built fine (although I'm
remote from the box right now so can't boot it yet); and gdb on the
vmlinux shows symbolic info is present.

Anyone remember, or object to reenabling CONFIG_DEBUG_INFO?

Thanks,
 Stephen

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: No CONFIG_DEBUG_INFO on x86_64 Xen; why not?
  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
  0 siblings, 1 reply; 3+ messages in thread
From: Keir Fraser @ 2006-04-06  8:51 UTC (permalink / raw)
  To: Stephen C. Tweedie; +Cc: xen-devel


On 6 Apr 2006, at 01:17, Stephen C. Tweedie wrote:

> neither of which are particularly helpful.  I've just completed a build
> with this change reverted and -g enabled and it built fine (although 
> I'm
> remote from the box right now so can't boot it yet); and gdb on the
> vmlinux shows symbolic info is present.
>
> 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.

  -- Keir

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: No CONFIG_DEBUG_INFO on x86_64 Xen; why not?
  2006-04-06  8:51 ` Keir Fraser
@ 2006-04-07  1:57   ` Stephen Tweedie
  0 siblings, 0 replies; 3+ messages in thread
From: Stephen Tweedie @ 2006-04-07  1:57 UTC (permalink / raw)
  To: Keir Fraser; +Cc: xen-devel

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2006-04-07  1:57 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 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.