Averting excessive oopses

Posted Nov 18, 2022 21:00 UTC (Fri) by unixbhaskar (guest, #44758)
Parent article: Averting excessive oopses

Well, in a wild hunch and armed with a lack of knowledge, may I suggest, it would be of great help, if and only if, the oops can point to the nearby location to look at(without going through the rigmarole of firing up the debugger to find out the culprit). I know, it requires some sort of system training to be built on to get it.

I am driving this notion by seeing it in different contexts in a specific environment.

See, I am looking for an "easy way out" than putting in any kind of effort. My lacuna.

Averting excessive oopses

Posted Nov 21, 2022 8:58 UTC (Mon) by jafd (subscriber, #129642) [Link]

Don't oopses provide a stack trace? Is this what you mean?

Averting excessive oopses

Posted Nov 21, 2022 10:44 UTC (Mon) by aaronmdjones (subscriber, #119973) [Link]

OOPSes already provide a stack trace and a full register dump. They also (if it was caused by e.g. the BUG_ON() macro) provide the file and line number that caused it.