From: Linus Torvalds <torvalds@linux-foundation.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>
Subject: Re: linux-next: Tree for Apr 10 (lib/test_printf.ko)
Date: Fri, 10 Apr 2020 13:13:12 -0700 [thread overview]
Message-ID: <CAHk-=whpvCqcCYvy=_v_F6NTtBSeQbXZ0iLr_smV2NJLT+XACw@mail.gmail.com> (raw)
In-Reply-To: <bfbcaa67-9656-3a80-fc66-c937297c8be0@infradead.org>
On Fri, Apr 10, 2020 at 12:41 PM Randy Dunlap <rdunlap@infradead.org> wrote:
>
> On 4/10/20 12:05 PM, Linus Torvalds wrote:
> >
> > That may be because of something like a DEBUG_INFO_REDUCED option.
>
> No, that's enabled. (see below)
That's kind of the point. DEBUG_INFO_REDUCED doesn't do the _full_ debug info.
And honestly, that's the right thing for 99% of all people. The full
debug info is _huge_. Enormous. It takes up lots of space, and it
makes for slower builds.
So normal people should use REDUCED.
But the full debug info does give some nicer debug stack traces with
dump_stack.sh, so for things like automated robots etc it's a great
thing.
> This is with FRAME_POINTER, not UNWIND_ORC. Maybe that's the difference?
That might cause the question marks and some additional uncertainty in
the underlying raw stack traces that the kernel reports, but no, it
shouldn't matter for what dump_stack.sh does.
Linus
next prev parent reply other threads:[~2020-04-10 20:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-10 3:27 linux-next: Tree for Apr 10 Stephen Rothwell
2020-04-10 16:35 ` linux-next: Tree for Apr 10 (lib/test_printf.ko) Randy Dunlap
2020-04-10 18:11 ` Linus Torvalds
2020-04-10 18:29 ` Randy Dunlap
2020-04-10 19:05 ` Linus Torvalds
2020-04-10 19:41 ` Randy Dunlap
2020-04-10 20:13 ` Linus Torvalds [this message]
2020-04-12 5:36 ` Naresh Kamboju
2020-04-12 6:22 ` Randy Dunlap
2020-04-14 19:26 ` Brendan Higgins
2020-04-15 18:55 ` Steven Rostedt
2020-04-15 19:16 ` Randy Dunlap
2020-04-15 19:28 ` Steven Rostedt
2020-04-12 3:46 ` linux-next: Tree for Apr 10 (warning: objtool: ___bpf_prog_run()) Randy Dunlap
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='CAHk-=whpvCqcCYvy=_v_F6NTtBSeQbXZ0iLr_smV2NJLT+XACw@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=rafael@kernel.org \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).