public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Harold L Hunt II <huntharo@msu.edu>
To: cygwin-xfree@cygwin.com
Subject: Re: Cygwin X server crashes when a remote Xemacs is run
Date: Wed, 12 Nov 2003 05:25:00 -0000	[thread overview]
Message-ID: <3FB1C452.3090309@msu.edu> (raw)
In-Reply-To: <DD77FDB0-14CE-11D8-A67A-000A95C46CA4@alumni.caltech.edu>

Anybody care to run a debug build of XWin.exe in gdb to find the crash 
location?

Harold

Brian R.Landy wrote:

> 
> Hi, I see what appears to be the same crash (address 0x61093b2c), using 
> Vim 6.2 with the GTK1 GUI.  One remote system is running AIX, the other 
> Solaris.  The cygwin system runs NT 4 SP6.
> 
> However, I only crash if I run XWin.exe -multiwindow.  Switching to 
> windowed, fullscreen, or even rootless causes the crash to go away.
> 
> Nothing is written to Xwin.log after the normal startup messages.
> 
> 
> Brian
> 
>> Here what I'm trying to do:
>> I establish a rsh connection with a UNIX/Linux machine and open an xterm.
>> The I run Xemacs on this remote machine and XWin.exe crashes.
>> I tried it connecting with both  a Linux machine and a Alpha machine. 
>> Here
>> the Xemacs versions installed on those machines:
>> Linux - Xemacs 21.1 (patch 14) i386-redhat-linux
>> Alpha - Xemacs 20.4 alpha-dec-osf3.2
>>
>> Here the Windows error message:
>> Exception: access violation (0xc0000005), Address: 0x61093b2c
>>
>> I'm running Cygwin 1.5.5-1 on Windows NT 4.0 Workstation. XWin.exe 
>> version
>> is 4.3.0-20
>>
>> Giampaolo Orrigo
> 
> 


  reply	other threads:[~2003-11-12  5:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-12  5:12 Brian R.Landy
2003-11-12  5:25 ` Harold L Hunt II [this message]
2003-11-12 20:16   ` landy
2004-03-12 19:26     ` Brian R. Landy
  -- strict thread matches above, loose matches on Subject: below --
2003-11-05 16:53 Orrigo, Giampaolo .

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=3FB1C452.3090309@msu.edu \
    --to=huntharo@msu.edu \
    --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).