On Thu, 19 Feb 2004, Poul-Henning Kamp wrote: [The problem turned out to be mainly controlling both undefined behaviour and standard behaviour with the same flag.] > Think if the 'A' option as userland SIGSEGV. (peter_at_ actually suggested > that I make it kill(getpid(), SIGSEGV) before calling abort in order > to let a process install a handler for it. Programs can already catch SIGABRT, and they probably need to be familiar with malloc's internals to trap its errors sort of safely, so it is reasonable to expect them to know what to trap. > I'm currently testing this patch: This would fix the original problem and some others. BruceReceived on Thu Feb 19 2004 - 01:36:07 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:43 UTC