On Fri, Apr 10, 2020 at 12:41 PM Randy Dunlap <rdunlap@xxxxxxxxxxxxx> 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
