Hello, On 2021-05-18 13:11, Jan Engelhardt wrote:
Unlike exit however, abort raises SIGABRT, which in normal circumstances should generate a coredump and hence a stacktrace is available that shows how execution even got there in the first place.
That is why I wrote about when those calls get compiled only when some special use case is configured (e.g. via "configure --with-assertions" or similar) that is only meant to be used e.g. by software developers but not in normal end-user environments. I.e. abort during runtime is useful for developers so that they can analyze the coredump how things failed but for normal end-users that user experience is really bad. Kind Regards Johannes Meixner -- SUSE Software Solutions Germany GmbH Maxfeldstr. 5 - 90409 Nuernberg - Germany (HRB 36809, AG Nuernberg) GF: Felix Imendoerffer