Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
crash sequence identified
I identified a sequence of Embitz crashing. It is reproducible on my side. What info is helpful besides the capture?

Attached Files Thumbnail(s)

.txt   crashrpt.txt (Size: 1.63 KB / Downloads: 46)

Yes, this is due to the fact that the jlink gdb server can't connect the device and is terminating while EB is still using the comm pipes. These kind of failures are hard to tackle. I personally don't use jlink's but I will try it myself.

Workaround, start jlink gdb manually and keep it open and disable the GDB server launch from EB. In this way you can verify from the GDB server dialog if a device connection is successful.

Forum Jump:

Users browsing this thread: 1 Guest(s)