--JP+T4n/bALQSJXh8
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Brian Stark wrote:
> #0  0x4851196b in kill () from /usr/lib/libc.so.12
> #1  0x484d6ca6 in pthread__assertfunc () from /usr/lib/libpthread.so.0
> #2  0x484d3518 in pthread__next () from /usr/lib/libpthread.so.0
> #3  0x484d33fd in pthread__block () from /usr/lib/libpthread.so.0
> #4  0x484d3f16 in pthread_mutex_lock () from /usr/lib/libpthread.so.0
> #5  0x484d3df3 in pthread_mutex_lock () from /usr/lib/libpthread.so.0

The above looks like a deadlock.

> #6  0x4856c484 in __cxa_atexit () from /usr/lib/libc.so.12
> #7  0x4856c65b in atexit () from /usr/lib/libc.so.12
> #8  0x0804c82e in ~AboutDialog (this=3D0x80724c0) at AboutDialog.C:29

I guess you have to unlock/release some lock before or in the
devastator.

> message in its destructor to trace entry/exit for the method, the
> destroy() method call takes care of destroying some motif resources).

Well, it might be a bug in motif. You might want to recompile your
libc with full debug information. That should help you find out
which mutexen the above refers to.

--=20
Christian

--JP+T4n/bALQSJXh8
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (NetBSD)

iD8DBQFAHOHU0KQix3oyIMcRAraJAJ44eK0M6qe+nYWsv6KEEwfjuWZHDACfSrIt
PPjto9jL9E8R4eHteLLNOqw=
=PLE8
-----END PGP SIGNATURE-----

--JP+T4n/bALQSJXh8--