Re: [LAD] Finding Deadlock causes in multithreaded C++ using gdb

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: <linux-audio-dev@...>
Date: Sunday, February 20, 2011 - 9:53 pm

--nextPart1864554.9CYOSvS7OA
Content-Type: Text/Plain;
charset="iso-8859-15"
Content-Transfer-Encoding: quoted-printable

On Sunday 20 February 2011 22:12:32 Harry Van Haaren wrote:

gdb is probably not the right tool for this. valgrinds helgrind is much bet=
ter=20
suited.
It also doesn't hurt to run one app in callgrind and memcheck every once in=
a=20
while...

Have fun,

Arnold

--nextPart1864554.9CYOSvS7OA
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEABECAAYFAk1hjVUACgkQuYLL1cDjHx1xzQCdFTiYnak66a0EDT+J7mVXwfxJ
9hAAni5irul6SDU3Bz7zCr/D9q2Ry2lD
=gUS6
-----END PGP SIGNATURE-----

--nextPart1864554.9CYOSvS7OA--

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
[LAD] Finding Deadlock causes in multithreaded C++ using gdb, Harry Van Haaren, (Sun Feb 20, 9:12 pm)
Re: [LAD] Finding Deadlock causes in multithreaded C++ using..., Gabriel M. Beddingfield, (Sun Feb 20, 10:46 pm)
Re: [LAD] Finding Deadlock causes in multithreaded C++ using..., Arnold Krille, (Sun Feb 20, 9:53 pm)