public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Nem W Schlecht <nem@emptec.com>
To: cygwin-xfree@cygwin.com
Subject: Re: xterm crashing when trying to access Ctrl-<mouse click> menu items
Date: Mon, 12 May 2014 14:37:00 -0000	[thread overview]
Message-ID: <CA+2x6-+RKs3B6wbwLMeXDXiwpmNwNdTCVQHyoZbFaKuR0TBU9w@mail.gmail.com> (raw)
In-Reply-To: <5370A3BB.8080300@dronecode.org.uk>

Thanks for the reply, Jon!  I'm happy you were able to reproduce the
issue - I assumed I had screwed something up in my environment. :)

Your attempted fix with rebase worked perfectly - all of my menus are
now working correctly.  If you'd like me to do any additional testing
in the future, don't hesitate to ask.

On Mon, May 12, 2014 at 5:34 AM, Jon TURNEY <jon.turney@dronecode.org.uk> wrote:
> On 05/05/2014 19:39, Nem W Schlecht wrote:
>>
>> For over a month now I've been having issues with my xterms in Cygwin.
>>   If I try to access *any* menu item under the Ctrl-<mouse button> menu
>> items (change font, turn on/off scrollbar, redraw window, etc.), my
>> xterm crashes the moment I un-press my mouse button.  I don't access
>> them all that often, so I don't know how long the issue has been
>> around, but it's been a couple of months now.
>>
>> I've tried launching it with an empty .Xdefaults file (home dir) and
>> by moving my .bashrc/.bash_profile files out of the way - still the
>> same result.  I've also gone out and downloaded the latest XTerm code
>> and have a version compiled with debugging, but my C skills are really
>> rusty and I'm not seeing anything terribly useful in gdb (I set my
>> CYGWIN env var to "error_start=dumper -d %1 %2" so I would get core
>> dumps).  I compiled a version with a different "DEFCLASS" set so that
>> I *know* it's not a bad resource or resource file.
>>
>> I'm running 64 bit on Windows 7.  More details in the attached
>> cygcheck.out.
>>
>> Anybody else on 64bit Cygwin / Win 7 having the same issues?
>
>
> Thanks for reporting this issue.  I can reproduce it.
>
> This appears to be an issue with Xt, as a Cygwin-specific patch does not
> work correctly on x86_64 when another DLL which is using Xt is loaded >2GB
> away from it.
>
> Until we have a fix, you *might* be able to work around this by rebasing the
> DLLs, e.g. in the specific case of xterm, which uses Xaw:
>
> cd /usr/bin
> rebase -v -b 0x400000000 cygXt-6.dll
> rebase -v -b 0x410000000 cygXaw-7.dll
>
> --
> Jon TURNEY
> Volunteer Cygwin/X X Server maintainer



-- 
Nem W Schlecht                   nem@emptec.com
Empyreal Technologies    http://www.emptec.com/
 "Perl did the magic.  I just waved the wand."

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


      reply	other threads:[~2014-05-12 14:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-05 18:39 Nem W Schlecht
2014-05-12 10:34 ` Jon TURNEY
2014-05-12 14:37   ` Nem W Schlecht [this message]

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=CA+2x6-+RKs3B6wbwLMeXDXiwpmNwNdTCVQHyoZbFaKuR0TBU9w@mail.gmail.com \
    --to=nem@emptec.com \
    --cc=cygwin-xfree@cygwin.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).