All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@linux.intel.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Andi Kleen <andi@firstfloor.org>,
	linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] Kbuild: Add a option to enable dwarf4
Date: Sun, 20 Jul 2014 14:17:30 -0700	[thread overview]
Message-ID: <20140720211729.GP5803@tassilo.jf.intel.com> (raw)
In-Reply-To: <20140720192315.GA4679@ravnborg.org>

On Sun, Jul 20, 2014 at 09:23:15PM +0200, Sam Ravnborg wrote:
> On Wed, Jul 16, 2014 at 01:16:12AM +0200, Andi Kleen wrote:
> > From: Andi Kleen <ak@linux.intel.com>
> > 
> > I found that a lot of unresolvable variables when using gdb on the kernel
> > become resolvable when dwarf4 is enabled. So add a Kconfig flag to enable it.
> > 
> > It definitely increases the debug information size, but on the other
> > hand this isn't so bad when debug fusion is used.
> 
> Would it not make sense to try to enable degug info like this:
> First try -gdwarf-4
> If this fails try -gdwarf-3
> If this fails try -gdwarf-2
> And if this also fails fallback to -g
> 
> We could then us a Kconfig option to enable the highest debug level - where 4 for now is the highest.
> On the other hand if most people have revent utils then they all have -gdwarf-4 supported
> and then it is no big deal.

I made it a separate option, because dwarf4 is somewhat bigger than dwarf3 and it's
probably only useful for people actively using gdb/crash
(and I don't think others users like systemtap/perf probe do dwarf4 yet)

If debug fusion was default it would be fine, but right now it would
need converting a lot of debuginfo packaing scripts first.

-Andi

  reply	other threads:[~2014-07-20 21:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-15 23:16 [PATCH 1/2] kbuild: Support split debug info v3 Andi Kleen
2014-07-15 23:16 ` [PATCH 2/2] Kbuild: Add a option to enable dwarf4 Andi Kleen
2014-07-20 19:23   ` Sam Ravnborg
2014-07-20 21:17     ` Andi Kleen [this message]
2014-07-20 19:04 ` [PATCH 1/2] kbuild: Support split debug info v3 Sam Ravnborg
2014-07-20 21:19   ` Andi Kleen
2014-07-23 18:05     ` Sam Ravnborg
2014-07-23 18:28       ` Andi Kleen
2014-07-24  8:10         ` Dirk Gouders
  -- strict thread matches above, loose matches on Subject: below --
2014-07-29 23:11 [PATCH 1/2] kbuild: Support split debug info v4 Andi Kleen
2014-07-29 23:11 ` [PATCH 2/2] Kbuild: Add a option to enable dwarf4 Andi Kleen
2014-07-30 13:38   ` Michal Marek
2014-05-16 22:06 [PATCH 1/2] kbuild: Support split debug info v3 Andi Kleen
2014-05-16 22:06 ` [PATCH 2/2] Kbuild: Add a option to enable dwarf4 Andi Kleen

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=20140720211729.GP5803@tassilo.jf.intel.com \
    --to=ak@linux.intel.com \
    --cc=andi@firstfloor.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.org \
    /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.