On Sun, Apr 22, 2007 at 12:10:33AM +0200, Andi Kleen wrote:
> > unwind code to even attempt to avoid the problem what should be done?
> > How about:
> >
> > (1) Make it clear the Fault Injection with STACKTRACE on x86_64 is at
> > best "Russian Roulette" -- maybe a !X86_64 in Kconfig.debug?
> >
On Sun, Apr 22, 2007 at 12:10:33AM +0200, Andi Kleen wrote:
unwind code to even attempt to avoid the problem what should be done?
How about:
(1) Make it clear the Fault Injection with STACKTRACE on x86_64 is at
best Russian Roulette -- maybe a !X86_64 in Kconfig.debug?
(2)
> There is no FRAME_POINTER support in the x86_64 code. Apparently it was
> removed when the unwind code was added but now that has been removed as
> well!
That's because no assembly code in x86-64 knows anything about frame pointers.
You will always get truncated traces if anything assembler is
On Fri, 2007-04-20 at 13:55 -0500, Scott Porter wrote:
> I'm attempting to use Fault Injection stacktrace filtering on an x86_64
> platform (see config details below) and finding problems:
>
> (1) Apparently stacktrace on x86_64 isn't always reliable but the fault
> injection code path to save a
On Fri, 2007-04-20 at 13:55 -0500, Scott Porter wrote:
I'm attempting to use Fault Injection stacktrace filtering on an x86_64
platform (see config details below) and finding problems:
(1) Apparently stacktrace on x86_64 isn't always reliable but the fault
injection code path to save a stack
There is no FRAME_POINTER support in the x86_64 code. Apparently it was
removed when the unwind code was added but now that has been removed as
well!
That's because no assembly code in x86-64 knows anything about frame pointers.
You will always get truncated traces if anything assembler is in
I'm attempting to use Fault Injection stacktrace filtering on an x86_64
platform (see config details below) and finding problems:
(1) Apparently stacktrace on x86_64 isn't always reliable but the fault
injection code path to save a stack trace looks *completely* unreliable
(2) CONFIG_NUMA and
I'm attempting to use Fault Injection stacktrace filtering on an x86_64
platform (see config details below) and finding problems:
(1) Apparently stacktrace on x86_64 isn't always reliable but the fault
injection code path to save a stack trace looks *completely* unreliable
(2) CONFIG_NUMA and
8 matches
Mail list logo
