From: Jon Turney <jon.turney@dronecode.org.uk>
To: cygwin@cygwin.com
Cc: "girish53@gmail.com >> Girish Joglekar" <girish53@gmail.com>
Subject: Re: Application not working in 64-bit cygwin cygwin/X
Date: Thu, 10 Mar 2016 17:05:00 -0000 [thread overview]
Message-ID: <56E1A93C.1040304@dronecode.org.uk> (raw)
In-Reply-To: <56E19B82.8050404@gmail.com>
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
next prev parent reply other threads:[~2016-03-10 17:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-10 15:58 Girish Joglekar
2016-03-10 16:06 ` Marco Atzeri
2016-03-10 17:05 ` Jon Turney [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-11-27 22:30 Girish Joglekar
2016-11-28 7:07 ` Ken Brown
2016-03-16 21:38 Girish Joglekar
2016-03-11 14:23 Girish Joglekar
2016-03-11 23:10 ` David Stacey
2016-03-12 6:28 ` Marco Atzeri
2016-03-12 17:39 ` Kaz Kylheku
2016-03-12 18:50 ` Corinna Vinschen
2016-03-15 13:14 ` cyg Simple
2016-02-23 16:35 Girish Joglekar
2016-02-23 15:12 Girish Joglekar
2016-02-23 15:51 ` Marco Atzeri
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56E1A93C.1040304@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin@cygwin.com \
--cc=girish53@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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).