mirror of
https://github.com/LadybirdBrowser/ladybird.git
synced 2025-07-29 04:09:13 +00:00
Kernel: Don't symbolicate stack traces in IRQ handlers
If we're capturing a stack trace in an IRQ handler, don't try to symbolicate it as we may not be able to access all pages.
This commit is contained in:
parent
62f615f0f4
commit
f6d1e45bf3
Notes:
sideshowbarker
2024-07-19 02:23:29 +09:00
Author: https://github.com/tomuta
Commit: f6d1e45bf3
Pull-request: https://github.com/SerenityOS/serenity/pull/3501
Issue: https://github.com/SerenityOS/serenity/issues/3495
1 changed files with 5 additions and 1 deletions
|
@ -857,7 +857,11 @@ String Thread::backtrace_impl()
|
|||
Vector<RecognizedSymbol, 128> recognized_symbols;
|
||||
|
||||
auto& process = const_cast<Process&>(this->process());
|
||||
auto elf_bundle = process.elf_bundle();
|
||||
OwnPtr<Process::ELFBundle> elf_bundle;
|
||||
if (!Processor::current().in_irq()) {
|
||||
// If we're handling IRQs we can't really safely symbolicate
|
||||
elf_bundle = process.elf_bundle();
|
||||
}
|
||||
ProcessPagingScope paging_scope(process);
|
||||
|
||||
// To prevent a context switch involving this thread, which may happen
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue