RGBCube/serenity
1
Fork 0
mirror of https://github.com/RGBCube/serenity synced 2025-10-31 05:52:46 +00:00
Code Issues Activity Actions

Kernel: Make failure to write coredump or perfcore a regular dmesg

Browse source 
This does not need to be a critical dmesg, as the system stays up
it makes more sense for it to be a normal dmesg message.

Luke mentioned this on discord, they really deserve the credit :^)

Reported-by: Luke Wilde <lukew@serenityos.org>
This commit is contained in:
Brian Gianforcaro 2022-08-09 20:17:42 -07:00
parent 9c42a75381
commit 00936e151e
1 changed files with 2 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

4
Kernel/Process.cpp
View file

@ -627,13 +627,13 @@ void Process::finalize()
if (m_should_generate_coredump) {
auto result = dump_core();
if (result.is_error()) {
critical_dmesgln("Failed to write coredump: {}", result.error());
dmesgln("Failed to write coredump for pid {}: {}", pid(), result.error());
}
}
if (m_perf_event_buffer) {
auto result = dump_perfcore();
if (result.is_error())
critical_dmesgln("Failed to write perfcore: {}", result.error());
dmesgln("Failed to write perfcore for pid {}: {}", pid(), result.error());
TimeManagement::the().disable_profile_timer();
}
}