On Sat, Dec 10, 2022 at 01:03:06 +0300, Valery Ushakov wrote: > KSYMS_RET? Then we can define separate DB_STGY_PROC (no heuristic) > and DB_STGY_RET (with the heuristic). > > The downside is that all MD db_stack_trace_print functions need to be > adjusted, but it actually makes sense to use both strategies there, > b/c when we are traversing an interrupt/exception frame, the > DB_STACK_PROC (without the heuristic) is the right thing to use, but > unwinding a call needs DB_STACK_RET (with the new flag).
PS: Grr. Obviously, I meant to say DB_STGY_PROC and DB_STGY_RET here. -uwe
