Hi,
is it necessary to use a tool like valgrind to debug deadlocks? For all
deadlocks I have seen it was enough to see the tracebacks of all threads
to diagnose the problem.
Could you please describe why this does not work in your case?
Thanks
Christoph
Am 25.06.2012 10:09, schrieb Marian
Am 29.06.2012 15:46, schrieb Alexander Potapenko:
This may be not that easy to guess which locks are taken when the
deadlock has already occurred.
However a Valgrind-like tool is really an overkill for deadlock
detection: a small library that interposes pthread_mutex_* (or other
locking
On Fri, Jun 29, 2012 at 5:50 PM, Christoph Bartoschek
bartosc...@or.uni-bonn.de wrote:
Am 29.06.2012 15:46, schrieb Alexander Potapenko:
This may be not that easy to guess which locks are taken when the
deadlock has already occurred.
However a Valgrind-like tool is really an overkill for
Am 29.06.2012 15:59, schrieb Alexander Potapenko:
Unfortunately in general there may be any number of locks and any set
of threads may wait for any of those locks.
Yes. I missed that. However I do not remember any situation where it
was not clear for me which locks caused a deadlock I had to
On Fri, 2012-06-29 at 17:46 +0400, Alexander Potapenko wrote:
This may be not that easy to guess which locks are taken when the
deadlock has already occurred.
However a Valgrind-like tool is really an overkill for deadlock
detection: a small library that interposes pthread_mutex_* (or other
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
10 matches
Mail list logo
