Re: C aggregate passing (Rust kernel policy)

[Steven Rostedt <rostedt@goodmis.org>]

On Wed, 26 Feb 2025 09:45:53 -0500
James Bottomley <James.Bottomley@HansenPartnership.com> wrote:

> >From some other rust boot system work, I know that the quality of a  
> simple backtrace in rust where you just pick out addresses you think
> you know in the stack and print them as symbols can sometimes be rather
> misleading, which is why you need an unwinder to tell you exactly what
> happened.

One thing I learned at GNU Cauldron last year is that the kernel folks use
the term "unwinding" incorrectly. Unwinding to the compiler folks mean
having full access to all the frames and variables and what not for all the
previous functions.

What the kernel calls "unwinding" the compiler folks call "stack walking".
That's a much easier task than doing an unwinding, and that is usually all
we need when something crashes.

That may be the confusion here.

-- Steve