DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=MkmaPNWOs/OPqIfFYNqelYY8ORyUP9j55E4nppmW9gud4NYfHjhIB
	ygZn6yg8xr6ABUc+rJkHl9fu0SBpMIb+LAO8awr/PzQjy8w8WRf0fMplOmWcf6jD
	GEaLdAr0/CUNyAhCiARDSw5OGRsaFbqvR+VpugHyD6+eMsIyN9ak1c=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Date: Wed, 13 Aug 2014 16:57:14 +0200
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: glib errors with latest gdb
Message-ID: <20140813145714.GK21106@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <53EB7607 DOT 3040004 AT cornell DOT edu>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;	protocol="application/pgp-signature"; boundary="xGGVyNQdqA79rdfn"
Content-Disposition: inline
In-Reply-To: <53EB7607.3040004@cornell.edu>
User-Agent: Mutt/1.5.23 (2014-03-12)

--xGGVyNQdqA79rdfn
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Aug 13 10:28, Ken Brown wrote:
> I'm getting errors with the latest gdb when trying to debug programs that
> depend on glib.  Here's an example, run from an xterm window:
>=20
> $ gdb /usr/bin/gvim
> GNU gdb (GDB) 7.8
> [...]
> Reading symbols from /usr/bin/gvim...(no debugging symbols found)...done.
> (gdb) r
> Starting program: /usr/bin/gvim
> [New Thread 4860.0x1b44]
> Traceback (most recent call last):
>   File "/usr/share/gdb/auto-load/usr/bin/cyggobject-2.0-0.dll-gdb.py", li=
ne
> 9, in <module>
>     from gobject import register
>   File "/usr/share/glib-2.0/gdb/gobject.py", line 3, in <module>
>     import gdb.backtrace
> ImportError: No module named backtrace

I see this error, too.  Unfortunately I'm not a python guru so this
is rather opaque to me.  gdb itself doesn't provide a gdb.backtrace
method, afaics.

However, despite this message, gvim starts normally.  And emacs-nox as
well as many other CLI applications can be started just fine, too.

But GDB hangs with emacs-X11 for some reason, even if I disable the
python modules.  From a quick GDB session it's not clear why this occurs :(

> Reverting to the previous gdb solves the problem.
>=20
> My actual use case involves emacs-w32 rather than gvim, but I tested gvim
> also to make sure that this wasn't emacs-specific.  The error is more than
> cosmetic, at least in the emacs case; gdb freezes and has to be killed fr=
om
> the Task Manager.

Oh well.  I'll try to find out why this occurs in the next couple of
days.  Why on earth is it always emacs, the exact opposite of a simple
testcase |(


Thanks,
Corinna

--=20
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

--xGGVyNQdqA79rdfn
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBAgAGBQJT63zKAAoJEPU2Bp2uRE+giWYP/3kb9978+C+7WqjZl6v8gtY9
Ptf/LMgondngWE9PIwEUe8v0qwswEDJxU5alv3KnS8SUQPm/ndHB3LtbQczNPx8s
NQUWA7fr5TkgsjbOb2gsKHh9ClNjhOvBBQt/oUUeyUpA+ik74/YdpaeUgfB1LdG3
68bA7klOiEqwHavbvvAghhPZY1LVNce5JlaB7OdjDH+IILs4teHy9WvZ8DEg93Eb
B7g8Wq6Q9cra0TlYk1QFMIqRHOlx2612nFyhrZxO76aovYGyu8oa4DSRL7O7tzms
kD/aCd9jS3B+omoJ7ufsfq8GV6YJcXoJ4vm/cPyVNnCa41R1z29Y/JcAZKFOBdut
ekvO+HROQ42jN9LJVbaR/JTxQEH7Whdx2StVzHh5wA/r9VOJrDhVPdFvpc6Dx7v6
PDHTpYacVbhm6UteW9l+FJtiVxVerCrBI/tO2vNsw22kHIe5wdM6GsuOHqy4mPXA
twu5XZE5aXujj5Xwlv4iUELamfsp6OjF0SzHOmlFRKABgoxhYA80zLvH/lPHZQ/q
m/rzZC0GlXmaw4knzPJuqk29tWCNq3PT8g2+I/zCkywwck0IqCv1c30PNnYgwZBl
W3y9ka3qVI+5/NItrsS0ZL98QRFYYdzrsbbACF1wVsZiZ3PQUNgSsrA62rOb2eZZ
2Yw323wp8rA44HT0gNNe
=PDuB
-----END PGP SIGNATURE-----

--xGGVyNQdqA79rdfn--