On Wed, Feb 12, 2014 at 2:14 PM, Nils Eliasson <nils.elias...@oracle.com> wrote: > On 2013-09-06 13:32, Mattis Castegren wrote: > > ... > > > > * Bigger changes > > - Re-structure hs_err file ... > > Yes, please move the compiler related info together. Having the current > compiler task separated from the compilation events with the heap regions > causes a lot of scrolling. > > > > * Additional Data > > ... > > > Make sure we read the OS-context when hitting asserts in debug-builds. Today > we only get registers, code and stack on actual crashes. Very valuable info > that is missing when investigating many test failures. >
I'm afraid that will be not possible. For a crash (i.e. because of a SIGSEGV) the kernel saves the context for the PC which caused the problem. 'assert' and 'guarantee' are macros which evaluate an expression and call report_vm_error if that expression was 'false'. I think the best we could do is to call 'getcontext()' after the evaluation of the expression, but that's not actually the context where the evaluation of the expression failed. But I agree that it may be helpful as well. And you should already get a complete stack trace for 'asserts' and 'guarantees' with the current implementation. Don't you see it? Regards, Volker > //Nils
