As mentioned in the title, since a short time the debugger is crashing reproducibly upon hitting a breakpoint. It does not happen at all breakpoints though. I have already tried to update the JLinkARM.dll file with the newest one from Segger. The call stack is displayed before the crash occurs (sometimes only empty entries for each stack frame).
I'm using e2 Studio 6.2.0, GCC ARM Embedded 6.2.1.20161205. Debugger is set to use SWD on a custom board with S5D5.
Any idea what to do about this?
Below you can find the call stack of the crash:
> msvcr100.dll!735fcc04()
[Unten angegebene Rahmen sind möglicherweise nicht korrekt und/oder fehlen, keine Symbole geladen für msvcr100.dll]
msvcr100.dll!735faf10()
msvcr100.dll!735fd6fd()
JLinkARM.dll!5158c57f()
JLinkARM.dll!515511e1()
JLinkARM.dll!5150b783()
JLinkARM.dll!514b6f52()
JLinkARM.dll!51563d16()
JLinkARM.dll!514b6913()
KernelBase.dll!756901e2()
msvcr100.dll!7358aaa1()
msvcr100.dll!73580949()
msvcr100.dll!7358260c()
KernelBase.dll!756901e2()
KernelBase.dll!7568d236()
KernelBase.dll!756901e2()
msvcp100.dll!67ad31d1()
msvcp100.dll!67acb487()
msvcr100.dll!7358016a()
msvcp100.dll!67ab30b8()
e2-server-gdb.exe!00b6d77e()
e2-server-gdb.exe!00b7d710()
e2-server-gdb.exe!00b7dee7()
e2-server-gdb.exe!00c6ce95()
e2-server-gdb.exe!00bbb660()
e2-server-gdb.exe!00bbf308()
e2-server-gdb.exe!00bbf72f()
e2-server-gdb.exe!00e4f94b()
e2-server-gdb.exe!00e50679()
e2-server-gdb.exe!00e5070e()
e2-server-gdb.exe!00bd41e7()
e2-server-gdb.exe!00bd41bb()
e2-server-gdb.exe!00bd4180()
e2-server-gdb.exe!00bd4142()
e2-server-gdb.exe!00e53c70()
msvcr100.dll!735cc556()
msvcr100.dll!735cc600()
kernel32.dll!76fe8744()
ntdll.dll!771058ed()
ntdll.dll!771058bd()