X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	q=dns; s=default; b=b/TwKvHpe12WNWO7/71ktPT5+LNVyG8jnoyBvZSaE65
	P6Pmt42sI6QNtPgRVfTJbKQBuVzjW83yJ/Yw92mvtmmHQAuJAaZV4D01eEWQrsyj
	91yUwc3HIx1N0fUrs2TbuPloivANrhkaUtSgbGCPPCvUa2Cjy7Qr+o9wJxthwL9c
	=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	s=default; bh=m8zCZk4wo49lfVgZhzGsdRl35D4=; b=J6eh+rhUa9xYVYysg
	7ziWgScdX+W8s47qy9KGvATTlqJKf/NYvpKyHJ5VgnMalBXxFJoC1fT0Dh8CntRG
	cvOIk/FRCZZJByjM+Nk7z807OKrX3APa1rvB4lbVg9Nyd+vJhLA17BX0xjwN6X8X
	b0gVjsI2wcjoSF9dFlb5uV5MYc=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=-3.1 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.2
X-HELO:	limerock02.mail.cornell.edu
X-CornellRouted:	This message has been Routed already.
Message-ID:	<54133E34.6010005@cornell.edu>
Date:	Fri, 12 Sep 2014 14:40:52 -0400
From:	Ken Brown <kbrown AT cornell DOT edu>
User-Agent:	Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: glib errors with latest gdb
References:	<53EB7607 DOT 3040004 AT cornell DOT edu> <20140813145714 DOT GK21106 AT calimero DOT vinschen DOT de> <20140828135712 DOT GV20700 AT calimero DOT vinschen DOT de> <54133542 DOT 80207 AT cornell DOT edu>
In-Reply-To:	<54133542.80207@cornell.edu>
X-IsSubscribed:	yes

On 9/12/2014 2:02 PM, Ken Brown wrote:
> Hi Corinna,
>
> On 8/28/2014 9:57 AM, Corinna Vinschen wrote:
>> On Aug 13 16:57, Corinna Vinschen wrote:
>>> 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:
>>>>
>>>> $ 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", line
>>>> 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 :(
>>
>> I reported the problem upstream in a bugzilla entry already handling
>> strange GDB hangs:
>>
>>    https://sourceware.org/bugzilla/show_bug.cgi?id=17247
>
> That bug appears to be something different.  But I managed to fix the
> problem without actually understanding the code.  I looked at cgf's
> patches from his build of gdb-7.6.50-4, and I noticed that some of his
> changes didn't make it into your gdb-7.8-1.src.patch.  The missing ones
> are collected in the attached "cgf.patch" file.
>
> If I apply that patch on top of your gdb-7.8-1.src.patch, the problem is
> gone.  (The python warning is still there, but it seems to be harmless.)

I'm not sure when Corinna will be back from vacation, but if anyone 
wants to test my fix in the meantime, you can get it from my Cygwin 
repository:

   http://sanibeltranquility.com/cygwin/

There are instructions at that URL.

Ken


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -