public inbox for
help / color / mirror / Atom feed
From: Carl Michal <>
Subject: Re: gtk+ applications crash when filechooser opened
Date: Fri, 03 Jan 2014 00:51:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Thu, 2 Jan 2014, Geoffrey Yerem wrote:

> On 1/2/2014 12:30 PM, Carl Michal wrote:
>>  On Thu, 2 Jan 2014, Geoffrey Yerem wrote:
>> >  Hello,
>> >      Has anyone found a resolution to this problem?  I've been
>> >  searching for weeks now and haven't been able to find a solution.  My
>> >  Cygwin installation has been broken ever since.
>>  I spent a little time trying to debug this a few weeks ago. I did
>>  confirm that the problem doesn't occur on x86_64. On x86 though, it
>>  looks like a Heisenbug - it behaved differently when running in the
>>  debugger, and differently depending on how you hit it in the debugger.
>>  To me it looked like it was buried somewhere in the threading library,
>>  but I didn't really get far enough along to say.
>>  Carl
> Hi Carl,
> 	For some reason this problem sounds like something I had to fix 
> before, but I can't really recall anything.  I was hoping it was related to a 
> bad configuration file somewhere that I could refresh.
> 	Right now it sounds like it's something that was upgraded recently, 
> but I have no way to track that down.  Do you think it's a bug in GTK+, or 
> another library?
> 	If there were any kind of workaround, that would help me immensely.
> Geoffrey

I think this is in pthreads, or glib. I don't think the problem is in gtk+ 

I haven't found any way around it yet except to use a 64-bit machine.


Unsubscribe info:
Problem reports:

  reply	other threads:[~2014-01-03  0:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-02 16:12 Geoffrey Yerem
2014-01-02 17:30 ` Carl Michal
2014-01-02 17:39   ` Geoffrey Yerem
2014-01-03  0:51     ` Carl Michal [this message]
     [not found] <>
2013-12-13 14:31 ` Ken Brown
2013-12-13 14:47   ` Corinna Vinschen
2013-12-13 19:02     ` Carl Michal

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).