Wel if you get SIGABRT then something called into abort() due to some error condition, which made the program exit immediately.
You should use the unit test debugging feature so that the debugger halts at the moment the test executable wants to throw that signal, and by looking at the call stack you should be able to see what the original cause is.
See documentation and topic.