From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.help Subject: Re: Cygwin emacs-x11 Won't Start During Windows Remote Desktop Session Date: Mon, 05 Oct 2015 21:01:26 +0300 Message-ID: <83zizxxki1.fsf@gnu.org> References: <20077799-fe10-49a9-ab55-43a9c784a6a3@googlegroups.com> NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1444068136 24890 80.91.229.3 (5 Oct 2015 18:02:16 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 5 Oct 2015 18:02:16 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Mon Oct 05 20:02:07 2015 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1ZjA5O-0001dY-GH for geh-help-gnu-emacs@m.gmane.org; Mon, 05 Oct 2015 20:02:06 +0200 Original-Received: from localhost ([::1]:47070 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZjA5N-0008Nk-EW for geh-help-gnu-emacs@m.gmane.org; Mon, 05 Oct 2015 14:02:05 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:58521) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZjA4r-0008Mr-Rf for help-gnu-emacs@gnu.org; Mon, 05 Oct 2015 14:01:34 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZjA4m-0006m2-SX for help-gnu-emacs@gnu.org; Mon, 05 Oct 2015 14:01:33 -0400 Original-Received: from mtaout20.012.net.il ([80.179.55.166]:38899) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZjA4m-0006lm-Kz for help-gnu-emacs@gnu.org; Mon, 05 Oct 2015 14:01:28 -0400 Original-Received: from conversion-daemon.a-mtaout20.012.net.il by a-mtaout20.012.net.il (HyperSendmail v2007.08) id <0NVR00F00DQ6RV00@a-mtaout20.012.net.il> for help-gnu-emacs@gnu.org; Mon, 05 Oct 2015 21:01:26 +0300 (IDT) Original-Received: from HOME-C4E4A596F7 ([84.94.185.246]) by a-mtaout20.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0NVR00FQKE2EQ420@a-mtaout20.012.net.il> for help-gnu-emacs@gnu.org; Mon, 05 Oct 2015 21:01:26 +0300 (IDT) In-reply-to: <20077799-fe10-49a9-ab55-43a9c784a6a3@googlegroups.com> X-012-Sender: halo1@inter.net.il X-detected-operating-system: by eggs.gnu.org: Solaris 10 X-Received-From: 80.179.55.166 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:107521 Archived-At: > Date: Mon, 5 Oct 2015 10:50:00 -0700 (PDT) > From: gtr289@gmail.com > > On my workplace PC running Windows 7 Enterprise I run cygwin-x as my x server (XWin.exe). From a linux box running redhat, I run the fvwm window manager. I frequently run a windows remote desktop session from my pc at home, to get my workplace desktop. The x-session is completely stable. However, I cannot run cygwin's emacs-x11. It starts up and keeps allocating memory (seen from the remote task-manager) until it core dumps after .5 Gig. > > Other cygwin-x apps start no problem, just as if I'm at work. Anyone know of a solution for this? Does it start OK if you invoke it with the -Q switch? If not, I suggest to ask on the Cygwin list first, and if no one has a clue there, attach GDB to Emacs while it "keeps allocating memory", and see what it does during that time. The results of this are best reported to bug-gnu-emacs@gnu.org. > Is there any run switch I can give emacs-x11 to debug what it's doing? It ends with a Fatal Error 11: Segmentation Fault. It does run in no-window mode with the -nw switch, but I'm hoping I can get full x support to work. If starting with -Q makes the problem disappear, try --debug-init (and without -Q), maybe you will see some error message that will give you a hint. If not, bisect your ~/.emacs init file until you find the problematic part, and investigate it (or ask here).