Is there any eay how to 'iterate' over all the current threads (let us
say that we know their thread id's - we do) and print their stack
traces? That would help us a lot.
One hack that might be worth a try is this. Your SIGTERM is sent by
the kernel first to Valgrind, which then sends it
Hello Julian,
this hack works excellently, and we've run the application under
valgrind successfully on Meizu M9 with Android 4.
Then, we tried the same on Motorola Razr with Android 2.3.6, but our
attempt to run the application under valgrind
failed very early.
The following message from
On Mon, 2012-06-25 at 11:03 +0200, Julian Seward wrote:
Is there any eay how to 'iterate' over all the current threads (let us
say that we know their thread id's - we do) and print their stack
traces? That would help us a lot.
One hack that might be worth a try is this. Your SIGTERM is
Do you have any ideas?
Not a clue, sorry.
J
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond.
You need to activate the Valgrind gdbserver for that, using options
--vgdb=yes (and possible give --vgdb-prefix=
to point at a file system supporting FIFOs).
Note that you should also be able to obtain the stack trace of
all threads using the standard gdbserver part of the android
