Re: Failure notice

[cygwinautoreply]

>  3 [main] zip2john 4752 find_fast_cwd: WARNING: Couldn't compute 
>FAST_CWD pointer.  Please report this problem to
>the public mailing list cygwin@cygwin.com
>ver 14  images.zip->File 13-11-2015 09 04 06.jpeg PKZIP Encr: 
>cmplen=2310085, decmplen=2315422, crc=4B8B28CB
>ver 14  images.zip->File 13-11-2015 09 54 10.jpeg PKZIP Encr: 
>cmplen=2031750, decmplen=2038334, crc=A966D71F
>ver 14  images.zip->File 13-11-2015 09 03 48.jpeg PKZIP Encr: 
>cmplen=2301539, decmplen=2306766, crc=37CBDCC9



https://cygwin.com/faq.html#faq.using.fixing-find_fast_cwd-warnings

--
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

Failure notice

[Andy Perkins]

 3 [main] zip2john 4752 find_fast_cwd: WARNING: Couldn't compute 
FAST_CWD pointer.  Please report this problem to

the public mailing list cygwin@cygwin.com
ver 14  images.zip->File 13-11-2015 09 04 06.jpeg PKZIP Encr: 
cmplen=2310085, decmplen=2315422, crc=4B8B28CB
ver 14  images.zip->File 13-11-2015 09 54 10.jpeg PKZIP Encr: 
cmplen=2031750, decmplen=2038334, crc=A966D71F
ver 14  images.zip->File 13-11-2015 09 03 48.jpeg PKZIP Encr: 
cmplen=2301539, decmplen=2306766, crc=37CBDCC9



--
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

Re: Fw: failure notice

[Brian Inglis]

On 2018-08-26 15:41, Thomas Wolff wrote:
>>    PS1="\[\e[1;32m\]\h \! $ \[\e[0m\] "
>> The real issue is that I still have no real clue on how these escape 
>> sequences work!! ...
> `man bash`, section PROMPTING
$ LESS='+/^\s*PROMPTING' man bash

Mostly provided with GNU programs, info often has more complete descriptions of
options and features than man pages, which may be brief for some GNU programs.

$ info bash 'Bash Features' Controlling

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.

--
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

Re: Fw: failure notice

[Thomas Wolff]

...

   PS1="\[\e[1;32m\]\h \! $ \[\e[0m\] "

The real issues is that I still have no real clue on how these escape
sequences work!! ...
`man bash`, section PROMPTING; the \[ and \] are not escape sequences 
for the terminal but meta syntax in the prompt, telling the shell that 
the string inside is an escape sequence and shall not be accounted for 
prompt line width. If you get that wrong, the shell will obviously be 
confused about its respective current position.


--
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

Fw: failure notice

[surendar jeyadev via cygwin]

rintable




Many thanks, TW, for your hint. I have "solved" the problem, but I do not
understand why it works! I took time to test it for a few days to make
sure that things were ok. Hence the slow response. If I had only also

included my prompt in the original email, I think that you would have
caught the error at once. My oversight.

Thomas Wolff wrote:>>

Please test the following:


* Set you prompt to some basic string, e.g. PS1=%. Does that change 

anything?* Mintty 2.7.5 changed the default wraparound behaviour to become
compatible with the xterm default. With setting -o OldWrapModes=true,
does that change anything?* Can you cross-test this in xterm?


* Does it happen in a freshly-started mintty? If it only happens later,
which programs did you run in the meantime?* Make a screen log demonstrating
a minimal test case, please.

<<




Trying the minimal prompt that you suggested, I did not have any terminal
problems.And then building up the prompt, but eschewing colour, I still did
not have probelms.That convinced me that, just as the webpage I quoted in
my original email suggested, the problem lay in the (incorrect!) escape
sequences to turn the prompts green.


My prompt, that I just copied off the internet was

  PS1="\e[1;32m\]\h \! $ \[\e[0m\] "

This is the cause of the problems. After a lot of hunting, I found another:


  PS1="\[\e[1;32m\]\h \! $ \[\e[0m\] "


And this works just fine!



The real issues is that I still have no real clue on how these escape
sequences work!! I read several pages that talk about how to get various
esoteric prmpts but none parses out the individual functional pieces. For
me, it is a case of "monkey see, monkey do".


Thanks again, TW.

--
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

Re: failure notice

[Brian Inglis]

On 2018-04-13 23:00, R0b0t1 wrote:
> On Fri, Apr 13, 2018 at 10:51 PM, Brian Inglis
>  wrote:
>> On 2018-04-13 21:10, Jeffrey Walton wrote:
 On Fri, Apr 13, 2018 at 8:36 PM, Jeffrey Walton  wrote:
> On Fri, Apr 13, 2018 at 7:51 AM, Corinna Vinschen
>  wrote:
>> On Apr 12 23:01, Jeffrey Walton wrote:
>>> I'm working on an AMD A6-9220 and seeing unusual results from
>>> /proc/cpuinfo. I think this may be an issue with the latest Cygwin. It
>>> may be present in earlier versions, too.
>>> Russinovich's coreinfo is shown below
>>> (https://docs.microsoft.com/en-us/sysinternals/downloads/coreinfo).
>>> Notice /proc/cpuinfo is missing aesni, pclmul, rdrand, SSE4.1, SSE4.2,
>>> AVX, etc.
>> Note that, in theory, cpuinfo has to be extended for each new CPU
>> generation.  That's a lot of work for marginal gain (Cygwin's not a real
>> kernel) so I'm doing this only very seldomly.
>> Patches welcome, of course!

I noticed that AMD cpuinfo lost cache size info at some point in the past.

> Thanks Corinna. I think I found the file of interest at fhandler_proc.cc.
> Whitespace is a bit off. It is a mix of tabs and space:
>   if (features1 & (1 << 0))
> print (" fpu");
>   if (features1 & (1 << 1))
> print (" vme");
> Should I perform a whitespace check-in before things begin? Or can you
> knock it out?
 The attachment is pp 572-74 from AMD's Programmer's Guide, Volume 3,
 General-Purpose and System Instructions (December 2017)
 (https://support.amd.com/TechDocs/24594.pdf). I believe it has the all
 the necessary information.
 Are there any objections to using it?

How else could AMD cpuid function results be decoded?
See also Appendix E Obtaining Processor Information Via the CPUID Instruction.

>>> Any ideas how to get this through? It is a three page PDF extracted from the
>>> AMD manual. It has the necessary information for the CPUID updates.
>> Just include the link to Appendix D section 2 from the ToC:
>> https://support.amd.com/TechDocs/24594.pdf#G14.931059

PDF readers e.g. {mu,q,x}pdf, gv, gsview, normally have ways to extract pages in
other formats; otherwise copy and paste can be used, preferably to a spreadsheet
program to handle tables properly, before saving in another format.

> He may be concerned about the longterm availability of the referenced 
> passages.

That document has snapshots on the Wayback machine at archive.org; but see
Appendix E Obtaining Processor Information Via the CPUID Instruction ibid.
https://support.amd.com/TechDocs/24594.pdf#G15.998445
"The information in this appendix supersedes the contents of the CPUID
Specification, order #25481, which is now obsolete."

One of the nice features of the amd64 cpuid instruction is that the architecture
is augmented to add meaning to formerly undefined or reserved functions, fields,
or bits, that can be used efficiently as specified, unlike the adhoc approaches
and lookups required for some i64 info.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

--
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

Re: failure notice

[R0b0t1]

On Fri, Apr 13, 2018 at 10:51 PM, Brian Inglis
 wrote:
> On 2018-04-13 21:10, Jeffrey Walton wrote:
>>> On Fri, Apr 13, 2018 at 8:36 PM, Jeffrey Walton  wrote:
 On Fri, Apr 13, 2018 at 7:51 AM, Corinna Vinschen
  wrote:
> On Apr 12 23:01, Jeffrey Walton wrote:
>> Hi Everyone,
>>
>> I'm working on an AMD A6-9220 and seeing unusual results from
>> /proc/cpuinfo. I think this may be an issue with the latest Cygwin. It
>> may be present in earlier versions, too.
>>
>> Russinovich's coreinfo is shown below
>> (https://docs.microsoft.com/en-us/sysinternals/downloads/coreinfo).
>> Notice /proc/cpuinfo is missing aesni, pclmul, rdrand, SSE4.1, SSE4.2,
>> AVX, etc.
>
> Note that, in theory, cpuinfo has to be extended for each new CPU
> generation.  That's a lot of work for marginal gain (Cygwin's not a real
> kernel) so I'm doing this only very seldomly.
>
> Patches welcome, of course!

 Thanks Corinna. I think I found the file of interest at fhandler_proc.cc.

 Whitespace is a bit off. It is a mix of tabs and space:

   if (features1 & (1 << 0))
 print (" fpu");
   if (features1 & (1 << 1))
 print (" vme");

 Should I perform a whitespace check-in before things begin? Or can you
 knock it out?
>>>
>>> The attachment is pp 572-74 from AMD's Programmer's Guide, Volume 3,
>>> General-Purpose and System Instructions (December 2017)
>>> (https://support.amd.com/TechDocs/24594.pdf). I believe it has the all
>>> the necessary information.
>>>
>>> Are there any objections to using it?
>> Any ideas how to get this through? It is a three page PDF extracted from the
>> AMD manual. It has the necessary information for the CPUID updates.
> Just include the link to Appendix D section 2 from the ToC:
> https://support.amd.com/TechDocs/24594.pdf#G14.931059
>

He may be concerned about the longterm availability of the referenced passages.

--
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

Re: failure notice

[Brian Inglis]

On 2018-04-13 21:10, Jeffrey Walton wrote:
>> On Fri, Apr 13, 2018 at 8:36 PM, Jeffrey Walton  wrote:
>>> On Fri, Apr 13, 2018 at 7:51 AM, Corinna Vinschen
>>>  wrote:
 On Apr 12 23:01, Jeffrey Walton wrote:
> Hi Everyone,
>
> I'm working on an AMD A6-9220 and seeing unusual results from
> /proc/cpuinfo. I think this may be an issue with the latest Cygwin. It
> may be present in earlier versions, too.
>
> Russinovich's coreinfo is shown below
> (https://docs.microsoft.com/en-us/sysinternals/downloads/coreinfo).
> Notice /proc/cpuinfo is missing aesni, pclmul, rdrand, SSE4.1, SSE4.2,
> AVX, etc.

 Note that, in theory, cpuinfo has to be extended for each new CPU
 generation.  That's a lot of work for marginal gain (Cygwin's not a real
 kernel) so I'm doing this only very seldomly.

 Patches welcome, of course!
>>>
>>> Thanks Corinna. I think I found the file of interest at fhandler_proc.cc.
>>>
>>> Whitespace is a bit off. It is a mix of tabs and space:
>>>
>>>   if (features1 & (1 << 0))
>>> print (" fpu");
>>>   if (features1 & (1 << 1))
>>> print (" vme");
>>>
>>> Should I perform a whitespace check-in before things begin? Or can you
>>> knock it out?
>>
>> The attachment is pp 572-74 from AMD's Programmer's Guide, Volume 3,
>> General-Purpose and System Instructions (December 2017)
>> (https://support.amd.com/TechDocs/24594.pdf). I believe it has the all
>> the necessary information.
>>
>> Are there any objections to using it?
> Any ideas how to get this through? It is a three page PDF extracted from the
> AMD manual. It has the necessary information for the CPUID updates.
Just include the link to Appendix D section 2 from the ToC:
https://support.amd.com/TechDocs/24594.pdf#G14.931059

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

--
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

Re: Fwd: failure notice

[Tom Kacvinsky]

Bump.  Any word on this?  We would like to solve this before our
customers run into the problem and having any diagnostics tips would
be greatly appreciated.  We are also in a bind because we have run
this by the Qt maintainers and they say they won't fix it.

Thanks,

Tom

On Mon, Jan 4, 2016 at 1:43 PM, Tom Kacvinsky
 wrote:
> On Tue, Dec 22, 2015 at 10:34 AM, Tom Kacvinsky
>  wrote:
>> It turns out we are using the 32 bit version of cygwin, so I am going
>> to try with 64 bit cygwin and the latest possible version and see how
>> I fare.
>
> Happens with both 32 and 64 bit cygwin.  I'm out of ideas.  The
> developer here that I have been working with seems to think this ia
> cygwin bug as this didn't happen in the 1.7 releases, and the version
> of Qt we are using hasn't changed in between the cygwin versions we
> are using.
>
> Any other ideas?  Is there an environment variable or debug option we
> can set to help track this down?

--
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

Re: Fwd: failure notice

[Tom Kacvinsky]

On Tue, Dec 22, 2015 at 10:34 AM, Tom Kacvinsky
 wrote:
> It turns out we are using the 32 bit version of cygwin, so I am going
> to try with 64 bit cygwin and the latest possible version and see how
> I fare.

Happens with both 32 and 64 bit cygwin.  I'm out of ideas.  The
developer here that I have been working with seems to think this ia
cygwin bug as this didn't happen in the 1.7 releases, and the version
of Qt we are using hasn't changed in between the cygwin versions we
are using.

Any other ideas?  Is there an environment variable or debug option we
can set to help track this down?

--
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

Re: Fwd: failure notice

[Tom Kacvinsky]

It turns out we are using the 32 bit version of cygwin, so I am going
to try with 64 bit cygwin and the latest possible version and see how
I fare.

--
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

Re: Fwd: failure notice

[Tom Kacvinsky]

On Tue, Dec 8, 2015 at 1:57 PM, Tom Kacvinsky
 wrote:
> 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.

While the application doesn't crash with a core dump even thought
assertion is triggered
(probably due to signal handlers installed by the Ada run time we
use), we do see this when
the application exits:

../../src/xcb_io.c:528: _XAllocID: Assertion `ret != inval_id' failed.

I don't know if this additional information is of use.

>
 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.
>

Do you want the libraries we have?  We have pinged Digia and they say
they won't look into this, especially considering Qt 4.8.x is EOL in
terms of support.

So, what are the next steps?

Thanks,

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

Re: Fwd: failure notice

[Tom Kacvinsky]

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 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?

>> 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.

Thanks for your time.

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

Re: Fwd: failure notice

[Jon Turney]

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 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.


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.

Steps to reproduce:

Build menus project
Execute menus excutable
Click on Edit to expand its menu
Move the cursor down the menu and expand Format
Move the cursor down the expanded menu and exit at the Center item
move cursor to hover over File node.
Menus app terminates


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?


--
Jon TURNEY
Volunteer Cygwin/X X Server maintainer

--
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

Re: Fwd: failure notice

[Tom Kacvinsky]

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

Re: Fwd: failure notice

[Tom Kacvinsky]

On Mon, Dec 7, 2015 at 10:19 AM, Jon Turney  wrote:
> On 04/12/2015 14:20, Tom Kacvinsky wrote:
>>
>> Hi,
>>
>> 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.

Thanks,

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

Re: failure notice

[Tom Kacvinsky]

Hi.

On Fri, Dec 4, 2015 at 9:20 AM, Tom Kacvinsky
 wrote:
> Hi,
>
> 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.
>

Bump.  We like to know about this because if we are running into
problems, our customers will, too.  I have an additional piece of
information.  What we've test is:

Multiple windows (Doesn't Work)
One window (Works)
Full screen (Works)
One window without title bar (Works)

--
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

Re: Fwd: failure notice

[Jon Turney]

On 04/12/2015 14:20, Tom Kacvinsky wrote:

Hi,

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.


--
Jon TURNEY
Volunteer Cygwin/X X Server maintainer

--
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

Re: Fwd: failure notice

[Tom Kacvinsky]

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:
>>>
>>> Hi,
>>>
>>> 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

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.

Steps to reproduce:

Build menus project
Execute menus excutable
Click on Edit to expand its menu
Move the cursor down the menu and expand Format
Move the cursor down the expanded menu and exit at the Center item
move cursor to hover over File node.
Menus app terminates

--
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

Fwd: failure notice

[Tom Kacvinsky]

Hi,

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.

Thanks,

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

Re: failure notice

[Mario Roy]

File locking is failing with Cygwin 2.4.0-0.2 as well. Thank you for
allowing the possibility of downgrading the Cygwin base package down
to 2.2.1-1 via setup.

Best regards,
Mario

--
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

Re: failure notice

[Theodore Si]

Thank you for your replies.

The permission of files under ~/.ssh can't be changed to 600 when
their group owner is None. I have to chgrp -R Users (or
Administrators, or any other group name other than None) ~/.ssh to
make it possible to run chmod on them. I suppose this is a bug of
cygwin on Windows 8/8.1 ?

I changed my GID in /etc/passwd from 513 to 544 to make my primary
group Administrators. Now the group owner of the files are turned to
? . Is it OK to do this?

On Sun, Nov 9, 2014 at 11:40 AM,  mailer-dae...@sourceware.org wrote:
 Hi. This is the qmail-send program at sourceware.org.
 I'm afraid I wasn't able to deliver your message to the following addresses.
 This is a permanent error; I've given up. Sorry it didn't work out.

 cygwin@cygwin.com:
 Invalid mime type text/html detected in message text or
 attachment.  Please send plain text messages only.
 See http://sourceware.org/lists.html#sourceware-list-info for more 
 information.
 Contact cygwin-ow...@cygwin.com if you have questions about this. (#5.7.2)

 --- Below this line is a copy of the message.

 Return-Path: sjyz...@gmail.com
 Received: (qmail 13527 invoked by uid 89); 9 Nov 2014 03:40:17 -
 Authentication-Results: sourceware.org; auth=none
 X-Virus-Checked: by ClamAV 0.98.4 on sourceware.org
 X-Virus-Found: No
 X-Spam-SWARE-Status: No, score=3.8 required=5.0 
 tests=BAYES_05,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS 
 autolearn=no version=3.3.2
 X-Spam-Status: No, score=3.8 required=5.0 
 tests=BAYES_05,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS 
 autolearn=no version=3.3.2
 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on sourceware.org
 X-Spam-Level: ***
 X-HELO: mail-oi0-f50.google.com
 Received: from mail-oi0-f50.google.com (HELO mail-oi0-f50.google.com) 
 (209.85.218.50)
  by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-SHA 
 encrypted) ESMTPS; Sun, 09 Nov 2014 03:40:15 +
 Received: by mail-oi0-f50.google.com with SMTP id v63so4113037oia.9
 for cygwin@cygwin.com; Sat, 08 Nov 2014 19:40:13 -0800 (PST)
 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:from:date:message-id:subject:to
  :content-type;
 bh=gLcsDdYrlI6xfgUXkVOcs/PuOHK4MCC7vay05Eu2bpE=;
 b=lVxGzQBup/DBjWJqJ4n1j4KiBPx4bCQYHTFo3oyOJAH4wMH76Oq0tyZL7trRtrbel9
  1SxN20Ody2bVMvKZD98LLL6wjiCevxs/LmmUjVPwec0FbRoA/Rx5YSMo5UHacOePTjwh
  SCC0vHBT9Wi7iiwuZIXvdWs0NYvkuBckOEEI4z8wYpbdvEBs2cmXf7L+QhmcbBXSkLVg
  n93rSczppuEmVTq0y8WzfTFLro2/NZ/ikToJQ3gNol+EwOhUahvjdMubZ5YHdM0RGvTJ
  DLZItS4U1gZshyODCtCrNoUNGX7XjrhYKNvxiywwCp7lcase660ufoKb9ugeb7MrExqV
  fS2Q==
 X-Received: by 10.182.32.33 with SMTP id f1mr18506071obi.34.1415504413720;
  Sat, 08 Nov 2014 19:40:13 -0800 (PST)
 MIME-Version: 1.0
 Received: by 10.60.59.197 with HTTP; Sat, 8 Nov 2014 19:39:43 -0800 (PST)
 In-Reply-To: 545ed9de.5010...@cygwin.com
 References: 545e36e5.5010...@gmail.com 545e420a.2020...@gmail.com 
 545ed9de.5010...@cygwin.com
 From: Theodore Si sjyz...@gmail.com
 Date: Sun, 9 Nov 2014 11:39:43 +0800
 Message-ID: 
 CAG=ehjo-ojefqnmysungewpkq1kpjnnaebs9axgkrcfuozk...@mail.gmail.com
 Subject: Re: Should the group of my user be None?
 To: cygwin@cygwin.com
 Content-Type: multipart/alternative; boundary=089e013a0796c206b7050764cd18

 --089e013a0796c206b7050764cd18
 Content-Type: text/plain; charset=UTF-8

 Thank you for your replies.

 The permission of files under ~/.ssh can't be changed to 600 when their
 group owner is None. I have to chgrp -R Users (or Administrators, or any
 other group name other than None) ~/.ssh to make it possible to run chmod
 on them. I suppose this is a bug of cygwin on Windows 8/8.1 ?

 I changed my GID in /etc/passwd from 513 to 544 to make my primary group
 Administrators. Now the group owner of the files are turned to ? . Is
 it OK to do this?

 On Sun, Nov 9, 2014 at 11:05 AM, Larry Hall (Cygwin) 
 reply-to-list-only...@cygwin.com wrote:

 On 11/08/2014 11:17 AM, Theodore Si wrote:

 Shouldn't I be in the group with the same name of my username, like in
 Linux?


 No.  Windows isn't Linux.  Of course, if you want to make a group with your
 user name and add your user to that group, Windows will probably let you do
 that.  But that's not a convention for user accounts on Windows.



 --
 Larry

 _

 A: Yes.
  Q: Are you sure?
  A: Because it reverses the logical flow of conversation.
  Q: Why is top posting annoying in email?

 --
 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



 --089e013a0796c206b7050764cd18
 Content-Type: text/html; charset=UTF-8
 Content-Transfer-Encoding: quoted-printable

 div dir=3DltrThank you for 

Re: failure notice

[Gary]

Yup, that's the output I get on my 32-bit windows machine, I'm not
seeing any value in environment for 'TERM'.
Are you referring to PATH?
%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;c:\cygwin\bin;c:\cygwin\usr\bin;c:\cygwin\sbin;c:\cygwin\usr\sbin;C:\Program
Files (x86)\OpenSSH\bin

--
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

failure notice

[_]

Hi. This is the smtp delivery program.
I'm afraid I wasn't able to deliver your message to the following addresses.
This is a permanent error; I've given up. Sorry it didn't work out.



mircea-duses...@klockmetal.com, directly server said: 553 mailbox not found



--- Below this line is a copy of the message.

Received: from dsldevice.lan ([63.216.117.32])
(envelope-sender cygwin@cygwin.com)
by 200.123.162.197 with ESMTP
for mircea-duses...@klockmetal.com; Fri, 10 Jul 2009 10:19:44 -0300
Received: from [63.216.117.32] by sourceware.org; Fri, 10 Jul 2009 23:38:05 
+0200
Date:   Fri, 10 Jul 2009 23:38:05 +0200
From:   Lindsey Nix cygwin@cygwin.com
X-Mailer: The Bat! (v3.80.03) Home
Reply-To: cygwin@cygwin.com
X-Priority: 3 (Normal)
Message-ID: 740830903.07145001973...@cygwin.com
To: mircea-duses...@klockmetal.com
Subject: Start earning the salary you deserve by obtaining the appropriate 
Univeristy Dergee.   based business home link news com
MIME-Version: 1.0
Content-Type: multipart/alternative;
  boundary=--AC6E7A52C67318FB
Sender: _...@pccorp.com.ar



--
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

Fwd: failure notice

[Gary Johnson]

What the heck is this?

Gary

- Forwarded message from [EMAIL PROTECTED] -

From: [EMAIL PROTECTED]
Subject: failure notice
Date: 24 Jul 2007 00:42:10 -
To: [EMAIL PROTECTED]

Hi. This is the qmail-send program at sourceware.org.
I'm afraid I wasn't able to deliver your message to the following addresses.
This is a permanent error; I've given up. Sorry it didn't work out.

cygwin-xfree@cygwin.com:
Sorry, your message has been denied due to keywords found in your
subject.  This is probably due to an off-topic post.
See http://sourceware.org/lists.html#sourceware-list-info for mailing list
info for this site.
Contact [EMAIL PROTECTED] if you have questions about this. (#5.7.2)

--- Enclosed are the original headers of the message.

From: Gary Johnson [EMAIL PROTECTED]
Subject: Re: help! cygwin window linux cmds dont work/ not recognised
Date: Mon, 23 Jul 2007 17:42:02 -0700
To: cygwin-xfree@cygwin.com
User-Agent: Mutt/1.5.16 (2007-06-09)

(Body suppressed)


- End forwarded message -

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

Re: Fwd: failure notice

[Christopher Faylor]

On Mon, Jul 23, 2007 at 05:46:43PM -0700, Gary Johnson wrote:
What the heck is this?

Sheesh.  Let's compound the problem, huh?

http://cygwin.com/ml/cygwin-xfree/2007-07/msg00033.html

If you want to discuss this move to another mailing list.

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

Re: failure notice

[James Supancic]

   I've been trying to get use an Xdmx server running on a Redhat box connected 
to a Cygwin X server on a laptop as a client.
   It starts up and I see the root window, but the functionality is not there. For 
example, if I drag a window off of the redhat box and onto the Cygwin box I can 
see the dotted outline of the window appear but the content wont display.



So... you are using an Xdmx server with two backends, one of which is
on a Linux box, the other of which is on a Windows box? That really
sounds like you are running without Xinerama support? Without Xinerama
you can't move windows between screens. Try this
DISPLAY=DMXHOST:DMXNUM.0 xev  DISPLAY=DMXHOST:DMXNUM.1 xev . If you
don't have Xinerama support you will get a xev window on each screen,
but you won't be able to move them between screens.

Did you try starting Xdmx with the +xinerama option on the command
line? This will enable Xinerama and allow you to move windows from one
screen to the other.

If +xinerama doesn't work, please post the complete command you are
using to launch Xdmx.



   Has anyone been using Xdmx and Cygwin together successfully and could you 
advise me on configuration issues?
   Also if you know of any reason why this is not going to work please let me 
know.



It should work, but it will be a bit harder to configure than
identical Linux boxes.

Thank you for your time,
James Steven Supancic III

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

FW: failure notice

[Hannu E K Nevalainen]

[EMAIL PROTECTED] wrote:
 Hi. This is the qmail-send program at _ource_are._rg.
 I'm afraid I wasn't able to deliver your message to the following
 addresses. This is a permanent error; I've given up. Sorry it didn't
 work out. 
 
 [EMAIL PROTECTED]:
 Sorry, your message has been denied due to keywords found in your
 subject.  This is probably due to an off-topic post or long-running
 flame war.
 See http://sourceware.org/lists.html#html-mail for mailing list
 info for this site.
 Contact [EMAIL PROTECTED] if you have questions about this.
 (#5.7.2) 
 
 --- Enclosed are the original headers of the message.

IRONIC
Phui!?  Hey that's ADVANCED!! ;-D


/Hannu E K Nevalainen, B.Sc. EE Microcomputer systems--72--

** mailing list preference; please keep replies on list **

-- printf(LocalTime: UTC+%02d\n,(DST)? 2:1); --
--END OF MESSAGE-BeginMessage---
(Body suppressed)
---End Message---
From: Hannu E K Nevalainen [EMAIL PROTECTED]
Sent: den 31 augusti 2004 20:22
To: ML Cygwin
Subject: List manager: space char stealth in subject line


THE PROBLEM:
As MS Outlook bases it's thread grouping of messages on the subject line only
 (AFAICS there isn't anything that uses the References: header)
the above leads to a split in FOUR threads - hard to read in correct order.

QUESTION: Am I the only person seeing this?

Why ask it here, you wonder? I see NOTHING like it from any other source.

Example: Current subject lines from cygwin-apps;
Re: [setup] Why does PackageSpecification haveaprivatecopy-constructor? (Robert?)
Re: [setup] Why does PackageSpecification have aprivatecopy-constructor? (Robert?)
Re: [setup] Why does PackageSpecification have aprivatecopy-constructor? (Robert?)
Re: [setup] Why does PackageSpecification have a privatecopy-constructor? (Robert?)
Re: [setup] Why does PackageSpecification have a privatecopy-constructor? (Robert?)
Re: [setup] Why does PackageSpecification have a privatecopy-constructor? (Robert?)
Re: [setup] Why does PackageSpecification have a private copy-constructor? (Robert?)

Seems to be related to _LONG_ subject lines too.

(Using MS Outlook 2000 SP-3, 9.0.0.6627)

/Hannu E K Nevalainen, B.Sc. EE Microcomputer systems--72-- 

** mailing list preference; please keep replies on list **

-- printf(LocalTime: UTC+%02d\n,(DST)? 2:1); --
--END OF MESSAGE--
--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

FW: failure notice

[Rajat Bawa]

Just wanted to know the support of the Cygwin utilities for 
 
- Files with Japanese data 
- Files with Japanese filenames 
 
 
Regards, 
Rajat Bawa

Re: failure notice

[Michael A Chase]

Try the ones you are interested in and see.

Please make any more such enquires to [EMAIL PROTECTED], that's where this
belongs unless you are offering patches to fix problems you have found.

--
Mac :})
** I normally forward private questions to the appropriate mail list. **
Ask Smarter: http://www.tuxedo.org/~esr/faqs/smart-questions.htm
Give a hobbit a fish and he eats fish for a day.
Give a hobbit a ring and he eats fish for an age.
- Original Message -
From: Rajat Bawa [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, January 28, 2002 02:31
Subject: FW: failure notice


 Just wanted to know the support of the Cygwin utilities for

 - Files with Japanese data 
 - Files with Japanese filenames





--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/