This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
Re: threads/1544: GNU/Linux GnomeMeeting threads invalid backtrace
- From: Damien Sandras <dsandras at seconix dot com>
- To: nobody at sources dot redhat dot com
- Cc: gdb-prs at sources dot redhat dot com,
- Date: 31 Mar 2004 19:18:01 -0000
- Subject: Re: threads/1544: GNU/Linux GnomeMeeting threads invalid backtrace
- Reply-to: Damien Sandras <dsandras at seconix dot com>
The following reply was made to PR threads/1544; it has been noted by GNATS.
From: Damien Sandras <dsandras@seconix.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: kk@verfaction.de, gdb-gnats@sources.redhat.com
Subject: Re: threads/1544: GNU/Linux GnomeMeeting threads invalid backtrace
Date: Wed, 31 Mar 2004 21:15:33 +0200
--=-y/7esD05XFyQ2O0FQH+R
Content-Type: text/plain; charset=iso-8859-15
Content-Transfer-Encoding: quoted-printable
Hello,
That is already the case. Any other tip?
Backtraces that we receiving coming from crashes with dynamically loaded
plugins always are incoherent...
Thanks,
Le ven, 06/02/2004 =E0 10:24 -0500, Daniel Jacobowitz a =E9crit :
> On Fri, Feb 06, 2004 at 10:31:06AM -0000, kk@verfaction.de wrote:
> > gcc.real (GCC) 3.3.3 20040125 (prerelease) (Debian)
> > This GDB was configured as "i386-linux".
>=20
> > >Description:
> > GnomeMeeting backtraces with PWLib plugins yield invalid backtraces.
> > Aswell for gdb -r gnomemeeting as gdb attach.
>=20
> I see that you're using Debian testing/unstable. In that case, try
> installing the latest GDB and libc6-dbg packages and backtracing again:
> gdb 6.0-6 and libc6-dbg 2.3.2.ds1-12. These include unwind tables for
> libc and libpthread, which permits much better accuracy.
>=20
> --=20
> Daniel Jacobowitz
> MontaVista Software Debian GNU/Linux Developer
--=20
_ Damien Sandras
(o- GnomeMeeting: http://www.gnomemeeting.org/
//\ FOSDEM: http://www.fosdem.org
v_/_ =20
=20
--=-y/7esD05XFyQ2O0FQH+R
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: Ceci est une partie de message
=?ISO-8859-1?Q?num=E9riquement?= =?ISO-8859-1?Q?_sign=E9e?=
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQBAaxjVdKWF9b5oMbURAhzJAKCnHrZEQCJtTZPjcIyg/IU9cYcz2wCeJWvg
Nvjz/xNsI+XqGzvxT1D8cDQ=
=kkp+
-----END PGP SIGNATURE-----
--=-y/7esD05XFyQ2O0FQH+R--