raise () libpthread-2.12.so 0x0000003DE2A0F6AB for__issue_diagnostic () libifcoremt.so.5 0x00002AFBB1E83348 for_emit_diagnostic () libifcoremt.so.5 0x00002AFBB1E83913 somefunc (somepar=somevalue) somefile.f90:1364 somebinary 0x00000000029EAA3BI am not completely sure but I believe it has not always been like that, but I don't know what could have changed in my setup. Can someone help me figure out what is going on here, and whether there's a possibility to make _my_ relevant code become frame 0 again?
If you get a segfault, for_emit_diagnostic would not be involved. That would be for errors detected at run-time such as array bounds violation. It's possible that if the stack got corrupted that a segfault might occur WHILE the diagnostic was trying to be put out, but that's much less common.
Yes - any error that is detected by tests in the code rather than the processor or OS. I don't know of a way to eliminate the intermediate frames.