2012/2/3 Thiago Jung Bauermann thiago.bauerm...@linaro.org:
Hi Barry,
On Thu, 2012-02-02 at 10:23 +0800, Barry Song wrote:
2. Why can’t the current gdb capture multithreads for android
processes? This question is actually about the theory for gdb to know
multi-threads. In my opinion, both
Barry Song 21cn...@gmail.com wrote.
2012/2/3 Ulrich Weigand ulrich.weig...@de.ibm.com:
However, from looking at the gdbserver sources provided with Android,
it seems there are some differences; in particular, there's this patch:
+/* Android doesn't have libthread_db.so.1, just
Ulrich,
thanks a lot!
2012/2/4 Ulrich Weigand ulrich.weig...@de.ibm.com:
Barry Song 21cn...@gmail.com wrote.
2012/2/3 Ulrich Weigand ulrich.weig...@de.ibm.com:
However, from looking at the gdbserver sources provided with Android,
it seems there are some differences; in particular, there's
Barry Song 21cn...@gmail.com wrote:
So my questions are:
1. Should I compile the native gdb using android toolchain and android
bionic/libthread libraries?
2. Why can’t the current gdb capture multithreads for android
processes? This question is actually about the theory for gdb to know
Hi Barry,
On Thu, 2012-02-02 at 10:23 +0800, Barry Song wrote:
2.Why can’t the current gdb capture multithreads for android
processes? This question is actually about the theory for gdb to know
multi-threads. In my opinion, both gnu and android use clone() to fork
threads and threads in
in system_server.
But if I compile a new program based on glibc and gnu libthread, I can
see multi-threads by the gdb.
So my questions are:
1. Should I compile the native gdb using android toolchain and android
bionic/libthread libraries?
2. Why can’t the current gdb capture multithreads
