Re: [Bug: 21.4.22] Sporadic crash entering a group with Gnus

From Emacs DEBUG the following life-saving advice: ** When you are trying to analyze failed assertions, it will be essential to compile Emacs either completely without optimizations or at least (when using GCC) with the -fno-crossjumping option. Failure to do so may make the compiler recycle the same abort call for all assertions in a given function, rendering the stack backtrace useless for identifying the specific failed assertion. I have tried to convince gcclib developers _not_ to declare the abort function as _noreturn_ since its sole function over exit(1) is to create a core dump and/or let a break point be set, and this is utterly useless if the compiler assumes that it can trash the stack and does not need to retain a recognizable return address.