0

I am trying to debug a complete halt error in the code inside a pure C++/OGL library that makes the GLRender thread stop completely. The usual tool for this is the DDMS and check where the thread is stopped at, but it seems unable to read the threads once inside the native library.

Is there any other way or tool I may be overlooking?

MLProgrammer-CiM
  • 17,231
  • 5
  • 42
  • 75
  • You need to use the ndk-gdb, rather than DDMS for native debugging. You may find though that it's faster to identify your problem by cleve r application of native calls to the Android logging functions. – Chris Stratton Sep 17 '13 at 17:24
  • I already have ndk-gdb available but the thread doesn't seem to stop, and a manual pause ends up in SEGFAULT after trying to reach the code. – MLProgrammer-CiM Sep 18 '13 at 09:41
  • In the end ndk-gdb did the trick. In the android debug view pause the gdb threadpool and look for the one actually running the code. – MLProgrammer-CiM Sep 18 '13 at 12:14
  • @EfEs You can add your solution as an answer to this question and accept it. – krsteeve Oct 07 '13 at 20:34

0 Answers0