From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9882 invoked by alias); 8 Dec 2015 18:57:29 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 9870 invoked by uid 89); 8 Dec 2015 18:57:29 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-0.6 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mail-ob0-f172.google.com Received: from mail-ob0-f172.google.com (HELO mail-ob0-f172.google.com) (209.85.214.172) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-GCM-SHA256 encrypted) ESMTPS; Tue, 08 Dec 2015 18:57:27 +0000 Received: by obbww6 with SMTP id ww6so19320631obb.0 for ; Tue, 08 Dec 2015 10:57:25 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=rC7EydX3yNOLrrSiTQVTmUePZv8QUSOQyZtnRqmxLsg=; b=kcDrYWI+hIUE6cvn2c00UKnSk6yD6F7kYQBDmVw6U+SUTBrm/f53Q42HJeLnqHSVc2 0mBQBg5GTETegAUYsaAxwfQQhbe1vAN9cSdS+RQWTOvOpgkIoGKa6/1XFEUMGaWgHzwk Tl4fjosABxcqbnsojhnVmZqp6INfPuz0lt5IflXj/uJLbTVx46A5iUz6ODd4lqMktofF 6EE2QFp4jglr/251RjIyLyzK8PVKL/EkBcF4XhY9QwWyCdEmDc6P3PBrudgcHNYUJNJ5 1OHrldf5iyRdsBriORjrzloEodAGL5uvBFfgfXpGJyh7QosnJFn1rjsyqKEC3u7Y6SkP 3LqQ== X-Gm-Message-State: ALoCoQkNZCI0U1BhYJYniBzwJKpjlW/14KW8BQJlaUzTYRgmv68zpVZpx3on1wLBxeTLEntH7CnWqjAcN825DXglA76HDbVioZWy5bC67x+IXl3nWPEaYXc= MIME-Version: 1.0 X-Received: by 10.182.120.37 with SMTP id kz5mr928112obb.81.1449601045615; Tue, 08 Dec 2015 10:57:25 -0800 (PST) Received: by 10.202.177.214 with HTTP; Tue, 8 Dec 2015 10:57:25 -0800 (PST) In-Reply-To: References: <56619fc2.83c1420a.10961.ffffb37fSMTPIN_ADDED_MISSING@mx.google.com> <5665A382.2050208@dronecode.org.uk> <56670A0B.5080707@dronecode.org.uk> Date: Tue, 08 Dec 2015 18:57:00 -0000 Message-ID: Subject: Re: Fwd: failure notice From: Tom Kacvinsky To: cygwin@cygwin.com Content-Type: text/plain; charset=UTF-8 X-IsSubscribed: yes X-SW-Source: 2015-12/txt/msg00105.txt.bz2 On Tue, Dec 8, 2015 at 11:55 AM, Tom Kacvinsky wrote: > On Tue, Dec 8, 2015 at 11:49 AM, Jon Turney wrote: >> On 07/12/2015 16:17, Tom Kacvinsky wrote: >>> >>> On Mon, Dec 7, 2015 at 10:24 AM, Tom Kacvinsky wrote: >>>> >>>> On Mon, Dec 7, 2015 at 10:19 AM, Jon Turney wrote: >>>>> >>>>> On 04/12/2015 14:20, Tom Kacvinsky wrote: >>>>>> >>>>>> We have an interesting problem whereby an Linux X client application >>>>>> crashes when running the X server on cygwin. We have a reproducer >>>>>> for the problem, but it is a Qt example application stored in a >>>>>> tarball. >>>>>> >>>>>> We have gathered the other information that would typically be >>>>>> requested. >>>>>> I just need to know the best way of getting this information to the >>>>>> list. >>>>> >>>>> >>>>> >>>>> If the tarball is being rejected by the mailing list, I'd suggest you >>>>> upload >>>>> it to some file hosting site and send a link to the mailing list. >>>>> >>>>> If that is really not possible for you (why?), you may, on this specific >>>>> occasion only, mail it directly to me. >>>> >>>> >>>> Hi Jon, >>>> >>>> That is totally do-able. I will get it on a hosting site and send the >>>> link. >>> >>> >>> Here is the DropBox link. >>> >>> https://www.dropbox.com/s/b6exaxm30j8q318/cygwin-x-repro.zip?dl=0 >> >> >> Sorry, I hadn't noticed that you are describing a crash in the Qt client, >> not the Cygwin X server. >> >> So, firstly, this is a Qt issue. It could be, since you aren't able to reproduce with Qt 4.8.1, but we can with 4.8.5 that we built. See below. >> >> It may well be that the multiwindow mode window manager for the Cygwin X >> server doesn't satisfy some expectation that Qt has (and I would be >> interested to know what that is), but Qt crashing is never the right >> thing to do. >> >> A backtrace of the Qt client when it crashes might be informative. >> > > Will attempt to get one. I recall seeing in our internal bug tracking system > the exact X server error message. Would that be of use? > There is no hard crash with a core dump so I can't get a backtrace. The client dies with no diagnostics - the GUI goes away and we return to the command prompt. >>> Please note it is a Qt reproducer. We have some hard coded paths in >>> the Makefile that you will need to modify. We are using Qt 4.8.6 >>> built on Ubuntu 12.04, 32 bit. >> >> Nevertheless, I tried your reproducer in a Ubuntu 12.04 32-bit VM, but >> wasn't able to observe any crash. >> >> I note that an Ubuntu 12.04 only seems to have Qt 4.8.1. Are you using a >> self-built Qt? > > Yes, we are using a self built Qt, pretty much a stock build, only thing we are > not doing is building the examples and demos. > We can provide the libraries we built and you can set LD_LIBRARY_PATH accordingly. Tom -- 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