Valery Ushakov writes: > On Thu, Feb 15, 2018 at 01:19:31 +0000, Sevan Janiyan wrote: > > > > I might/would suggest > > > > > > OPTIONS DDB_ONPANIC=2 > > > > clear, any reason not to have this as a default? (I'm going to sleep on it) > > As someone has already mentioned upthread, because printing a > backtrace might cause another panic, so the default was selected to be > on the safe(r) side. At least that's what I recall.
i don't think this is the case. the builtin stack trace code is fault-tolerant. if it faults, it will not re-try and you'll get a db> prompt. AFAIR, this support was added and the default left alone, not beacuse the old/current default is right, but that there was pushback from people who wanted the old style. .mrg
