Application not working in 64-bit cygwin cygwin/X

Application not working in 64-bit cygwin cygwin/X

[Girish Joglekar]

Thank you for taking a look at the tar file. I apologize for the big
'test' problem. The code is so interlinked that it would have taken me
a lot longer to separate out only the relevant code. I will add Wall.
Hope you are able to reproduce the problem.
Girish

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

Application not working in 64-bit cygwin cygwin/X

[Girish Joglekar]

I had submitted a possible bug report in March 2016 and a link to tar
file with source code. David Stacey had reproduced my problem. I
downloaded the latest version of cygwin two days ago. The problem
still persists. Can some one advise me whether I should expect some
help from the cygwin experts. I can submit the source code again if
necessary.
Very frustrated.
Girish

--
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: Application not working in 64-bit cygwin cygwin/X

[Ken Brown]

On 11/26/2016 6:51 PM, Girish Joglekar wrote:
> I had submitted a possible bug report in March 2016 and a link to tar
> file with source code. David Stacey had reproduced my problem. I
> downloaded the latest version of cygwin two days ago. The problem
> still persists. Can some one advise me whether I should expect some
> help from the cygwin experts. I can submit the source code again if
> necessary.

If you think your crash is due to a Cygwin bug, then you need to try to 
write a small test case that exhibits the problem.  Marco told you that 
last February, and this was your reply 
(https://cygwin.com/ml/cygwin/2016-02/msg00368.html):

> The code is so interlinked that it would have taken me
> a lot longer to separate out only the relevant code.

You have to show some willingness to spend time on this problem yourself 
if you hope to get help from the Cygwin experts.

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

Application not working in 64-bit cygwin cygwin/X

[Girish Joglekar]

I ran the TEST.x through gdb. The program dies at line 1709 in the
ifdef XTHREADS branch.

1695    XmRenderTableCopy(XmRenderTable table,
1696                      XmStringTag *tags,
1697                      int tag_count)
1698    {
1699      XmRenderTable         rt = NULL;
1700      _XmRenderTable        t = NULL;
1701      int                   i, j, count;
1702      int                   size;
1703      XmRendition           rend = NULL;
1704      XtAppContext          app = NULL;
1705
(gdb) l
1706      if (table == NULL) return((XmRenderTable)NULL);
1707
1708    #ifdef XTHREADS
1709      if (_XmRTDisplay(table))
1710         app = XtDisplayToApplicationContext(_XmRTDisplay(table));
1711      if (app) {
1712         _XmAppLock(app);
1713      }
1714      else {
1715         _XmProcessLock();
(gdb) l
1716      }
1717    #endif

I compared it to a snippet I found at
https://www.opengroup.org/infosrv/openmotif/R2.1.30/motif/lib/Xm/XmFontList.c
Should it be
    if(_XmRTDisplay((XmRenderTable)table))
             app =
XtDisplayToApplicationContext(_XmRTDisplay((XmRenderTable)table))

Just a thought.
Girish

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

Application not working in 64-bit cygwin cygwin/X

[Girish Joglekar]

I have cleaned up the test example based on X-Windows/Motif which crashes
on 64-bit cygwin cygwin/X but runs on the 32-bit version. The only
warnings are of the type 'variable set but not used'.

Here is the link to the tar file.

https://www.dropbox.com/s/lknuoac64hfql4s/test.tar?dl=0

Hope you can reproduce the behavior and fix the problem.

Suggested steps: Start X. After extracting the contents of the tar
file go into the folder and enter
make install
It creates TEST.x. Enter TEST.x at the prompt, which opens a dialog
box with two buttons. Click on the Open button. When it works, it
opens another dialog box. When it crashes it gives Segmentation Fault.

Please let me know the fix.
Thank you.
Girish

--
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: Application not working in 64-bit cygwin cygwin/X

[David Stacey]

On 11/03/16 14:23, Girish Joglekar wrote:
> I have cleaned up the test example based on X-Windows/Motif which crashes
> on 64-bit cygwin cygwin/X but runs on the 32-bit version. The only
> warnings are of the type 'variable set but not used'.
>
> Here is the link to the tar file.
>
> https://www.dropbox.com/s/lknuoac64hfql4s/test.tar?dl=0
>
> Hope you can reproduce the behavior and fix the problem.

I tried this on Fedora 23 64-bit and it works. I had to add an empty 
utcrcu.h file, as the code tries to #include this, and it doesn't exist 
in the tar file. Given that it runs in 64-bit Linux, the problem is 
unlikely to be an issue associated with porting 32-bit applications to 
64-bit.

Dave.


--
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: Application not working in 64-bit cygwin cygwin/X

[Marco Atzeri]

On 12/03/2016 00:10, David Stacey wrote:
> On 11/03/16 14:23, Girish Joglekar wrote:
>> I have cleaned up the test example based on X-Windows/Motif which crashes
>> on 64-bit cygwin cygwin/X but runs on the 32-bit version. The only
>> warnings are of the type 'variable set but not used'.
>>
>> Here is the link to the tar file.
>>
>> https://www.dropbox.com/s/lknuoac64hfql4s/test.tar?dl=0
>>
>> Hope you can reproduce the behavior and fix the problem.
>
> I tried this on Fedora 23 64-bit and it works. I had to add an empty
> utcrcu.h file, as the code tries to #include this, and it doesn't exist
> in the tar file. Given that it runs in 64-bit Linux, the problem is
> unlikely to be an issue associated with porting 32-bit applications to
> 64-bit.
>
> Dave.
>

it can be a bug not triggered on linux due the difference in managing 
function arguments in the stack.

I catch one some time ago in netcdf
https://cygwin.com/ml/cygwin/2015-11/msg00102.html

Of course it can also be a bug in Xt itself.

Regards
Marco


--
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: Application not working in 64-bit cygwin cygwin/X

[Kaz Kylheku]

On 11.03.2016 22:27, Marco Atzeri wrote:
> On 12/03/2016 00:10, David Stacey wrote:
>> On 11/03/16 14:23, Girish Joglekar wrote:
>>> I have cleaned up the test example based on X-Windows/Motif which 
>>> crashes
>>> on 64-bit cygwin cygwin/X but runs on the 32-bit version. The only
>>> warnings are of the type 'variable set but not used'.
>>> 
>>> Here is the link to the tar file.
>>> 
>>> https://www.dropbox.com/s/lknuoac64hfql4s/test.tar?dl=0
>>> 
>>> Hope you can reproduce the behavior and fix the problem.
>> 
>> I tried this on Fedora 23 64-bit and it works. I had to add an empty
>> utcrcu.h file, as the code tries to #include this, and it doesn't 
>> exist
>> in the tar file. Given that it runs in 64-bit Linux, the problem is
>> unlikely to be an issue associated with porting 32-bit applications to
>> 64-bit.
>> 
>> Dave.
>> 
> it can be a bug not triggered on linux due the difference in managing
> function arguments in the stack.

Among a myriad other things! Undefined behaviors can have totally 
different consequences even on architecturally similar systems. E.g. a 
malloced
buffer overrun depends on the heap structure and allocation pattern
driven by program inputs. Uninitialized memory will have different 
garbage
in it. And so on.

So it works on Fedora 23 64-bit? That could be by fluke.

How about this: does it run with zero errors under Valgrind on the same 
system?

That represents a greater confidence that "it works".

In any case, this is a poor approach to problem solving in the
context of open source:

"Hi, on your platform the program in my multi-megabyte archive crashes
... somewhere in the code (I could tell you where, but I can't be 
bothered
to use the debugger). Please download the whole, reproduce the problem, 
and
debug it for me."

This kind of burp-and-diaper changing is done in the industry only for
paying customers.

--
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: Application not working in 64-bit cygwin cygwin/X

[Corinna Vinschen]

[-- Attachment #1: Type: text/plain, Size: 2846 bytes --]

On Mar 12 09:38, Kaz Kylheku wrote:
> On 11.03.2016 22:27, Marco Atzeri wrote:
> >On 12/03/2016 00:10, David Stacey wrote:
> >>On 11/03/16 14:23, Girish Joglekar wrote:
> >>>I have cleaned up the test example based on X-Windows/Motif which
> >>>crashes
> >>>on 64-bit cygwin cygwin/X but runs on the 32-bit version. The only
> >>>warnings are of the type 'variable set but not used'.
> >>>
> >>>Here is the link to the tar file.
> >>>
> >>>https://www.dropbox.com/s/lknuoac64hfql4s/test.tar?dl=0
> >>>
> >>>Hope you can reproduce the behavior and fix the problem.
> >>
> >>I tried this on Fedora 23 64-bit and it works. I had to add an empty
> >>utcrcu.h file, as the code tries to #include this, and it doesn't exist
> >>in the tar file. Given that it runs in 64-bit Linux, the problem is
> >>unlikely to be an issue associated with porting 32-bit applications to
> >>64-bit.
> >>
> >>Dave.
> >>
> >it can be a bug not triggered on linux due the difference in managing
> >function arguments in the stack.
> 
> Among a myriad other things! Undefined behaviors can have totally different
> consequences even on architecturally similar systems. E.g. a malloced
> buffer overrun depends on the heap structure and allocation pattern
> driven by program inputs. Uninitialized memory will have different garbage
> in it. And so on.
> 
> So it works on Fedora 23 64-bit? That could be by fluke.
> 
> How about this: does it run with zero errors under Valgrind on the same
> system?
> 
> That represents a greater confidence that "it works".
> 
> In any case, this is a poor approach to problem solving in the
> context of open source:
> 
> "Hi, on your platform the program in my multi-megabyte archive crashes
> ... somewhere in the code (I could tell you where, but I can't be bothered
> to use the debugger). Please download the whole, reproduce the problem, and
> debug it for me."
> 
> This kind of burp-and-diaper changing is done in the industry only for
> paying customers.

Heh.  Just for completeness, though, I would like to point out the FAQ I
wrote back when 64 bit Cygwin was still in development:

https://cygwin.com/faq/faq.html#faq.programming.64bitporting

There are a couple of points there which might be interesting.

Additionally we have some experience with actual bugs in the code which
were covered in Linux but showed up on Cygwin.  A prominent example was
a missing declaration of a stdargs function in OpenLDAP which led to
different results on Linux (working) and Cygwin (crashing) because of a
subtil difference in the ABI (6 argument registers in SysV-ABI vs. 4
register arguments in the MS-ABI.


Corinna

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

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

Re: Application not working in 64-bit cygwin cygwin/X

[cyg Simple]

On 3/12/2016 12:38 PM, Kaz Kylheku wrote:
> 
> This kind of burp-and-diaper changing is done in the industry only for
> paying customers.
> 

Thanks Kaz, I can now use a new tag line:

"I don't do BADC for free!"

:D LOL

-- 
cyg Simple

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

Application not working in 64-bit cygwin cygwin/X

[Girish Joglekar]

My application runs on cygwin, cygwin/X 32-bit but does not run on
64-bit on Windows 10. The dump from segmentation faults says:

Exception: STATUS_ACCESS_VIOLATION at rip=003F9919D22
rax=0000000000000001 rbx=0000000600277300 rcx=0000000000275620
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000275620
r8 =0000000000000000 r9 =0000000000000000 r10=0000000100000000
r11=00000003F9CF12AB r12=00000000FFFFB200 r13=0000000000000000
r14=0000000600277710 r15=0000000000000000
rbp=0000000600277300 rsp=00000000FFFFA410
program=C:\BPTECH\batches\versn7_2\execs\BATCHES.x, pid 7396, thread main
cs=0033 ds=002B es=002B fs=0053 gs=002B ss=002B

Cygwin FAQ says that this could be due to two different versions of
cygwin1.dll. However there is only one copy on my machine.

Please advise. I had posted a test problem on Feb 23. I do not know if
you were able to reproduce the behavior. I am completely stuck at this
point and cannot move forward. Any suggestions are welcome.
Girish

--
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: Application not working in 64-bit cygwin cygwin/X

[Marco Atzeri]

On 10/03/2016 16:58, Girish Joglekar wrote:
> My application runs on cygwin, cygwin/X 32-bit but does not run on
> 64-bit on Windows 10. The dump from segmentation faults says:
>
> Exception: STATUS_ACCESS_VIOLATION at rip=003F9919D22
> rax=0000000000000001 rbx=0000000600277300 rcx=0000000000275620
> rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000275620
> r8 =0000000000000000 r9 =0000000000000000 r10=0000000100000000
> r11=00000003F9CF12AB r12=00000000FFFFB200 r13=0000000000000000
> r14=0000000600277710 r15=0000000000000000
> rbp=0000000600277300 rsp=00000000FFFFA410
> program=C:\BPTECH\batches\versn7_2\execs\BATCHES.x, pid 7396, thread main
> cs=0033 ds=002B es=002B fs=0053 gs=002B ss=002B
>
> Cygwin FAQ says that this could be due to two different versions of
> cygwin1.dll. However there is only one copy on my machine.
>
> Please advise. I had posted a test problem on Feb 23. I do not know if
> you were able to reproduce the behavior. I am completely stuck at this
> point and cannot move forward. Any suggestions are welcome.
> Girish
>

The test case you provided was too large and have too many
compilation warnings.

If you eliminate all the compilation warning and than still crash,
may be someone will look on it.

Regards
Marco


--
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: Application not working in 64-bit cygwin cygwin/X

[Jon Turney]

On 10/03/2016 16:06, Marco Atzeri wrote:
> On 10/03/2016 16:58, Girish Joglekar wrote:
>> My application runs on cygwin, cygwin/X 32-bit but does not run on
>> 64-bit on Windows 10. The dump from segmentation faults says:
>>
>> Exception: STATUS_ACCESS_VIOLATION at rip=003F9919D22
>> rax=0000000000000001 rbx=0000000600277300 rcx=0000000000275620
>> rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000275620
>> r8 =0000000000000000 r9 =0000000000000000 r10=0000000100000000
>> r11=00000003F9CF12AB r12=00000000FFFFB200 r13=0000000000000000
>> r14=0000000600277710 r15=0000000000000000
>> rbp=0000000600277300 rsp=00000000FFFFA410
>> program=C:\BPTECH\batches\versn7_2\execs\BATCHES.x, pid 7396, thread main
>> cs=0033 ds=002B es=002B fs=0053 gs=002B ss=002B
>>
>> Cygwin FAQ says that this could be due to two different versions of
>> cygwin1.dll. However there is only one copy on my machine.
>>
>> Please advise. I had posted a test problem on Feb 23. I do not know if
>> you were able to reproduce the behavior. I am completely stuck at this
>> point and cannot move forward. Any suggestions are welcome.
>> Girish
>>
>
> The test case you provided was too large and have too many
> compilation warnings.
>
> If you eliminate all the compilation warning and than still crash,
> may be someone will look on it.
See also https://cygwin.com/faq.html#faq.programming.64bitporting

Using int, long and pointers interchangeably will not work well with 
libXt on any 64-bit OS.


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

Application not working in 64-bit cygwin cygwin/X

[Girish Joglekar]

I have created a test example based on X-Windows/Motif which crashes
on 64-bit cygwin cygwin/X but runs on the 32-bit version.

Here is the link to the tar file. Please download it before the link
expires (I do not know now long it stays active)

https://www.dropbox.com/s/lknuoac64hfql4s/test.tar?dl=0

Hope you can reproduce the behavior and fix the problem.

Suggested steps: Start X. After extracting the contents of the tar
file go into the folder and enter
make install
It creates TEST.x. Enter TEST.x at the prompt, which opens a dialog
box with two buttons. Click on the Open button. When it works, it
opens another dialog box. When it crashes it gives Segmentation Fault.

Please let me know the fix.
Thank you.
Girish

--
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: Application not working in 64-bit cygwin cygwin/X

[Marco Atzeri]

On 23/02/2016 16:12, Girish Joglekar wrote:
> I have created a test example based on X-Windows/Motif which crashes
> on 64-bit cygwin cygwin/X but runs on the 32-bit version.
>
> Here is the link to the tar file. Please download it before the link
> expires (I do not know now long it stays active)
>
> https://www.dropbox.com/s/lknuoac64hfql4s/test.tar?dl=0
>
> Hope you can reproduce the behavior and fix the problem.
>

Hi Girish,
May I suggest you add the -Wall flags to  INFLAGS
and look at all the mismatched definitions ?

there are almost 200 warnings... not counting the unused variables

marco@GE-MATZERI-EU /pub/temp/X_test/test
  64 $ grep warning make.log |wc -l
260

marco@GE-MATZERI-EU /pub/temp/X_test/test
  64 $ grep "warning: unused"  make.log |wc -l
72

Usually a test case is simple not 116 source files.

Regads
Marco


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