Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Message-ID: <3A0F9044.2E387F2F@ece.gatech.edu> Date: Mon, 13 Nov 2000 01:55:00 -0500 From: Charles Wilson X-Mailer: Mozilla 4.75 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: XEmacs on cygwin wierdness References: <3A0F7709 DOT F8ED68FF AT ece DOT gatech DOT edu> <20001113000953 DOT A4917 AT redhat DOT com> <3A0F827C DOT 15675931 AT ece DOT gatech DOT edu> <20001113010018 DOT A6535 AT redhat DOT com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Christopher Faylor wrote: > >I got a popup saying "Program received signal SIGSEGV, Segmentation fault" > >Stack window shows "_size_of_stack_reserve__" > > That is the symbol that gdb seems to use when it can't find anything > else to use. What address is associated with this? Is this the only > thing in the stack window? There aren't any other addresses being > displayed? How about the .stackdump file? That's pretty much it: _size_of_stack_reserve__ is the only thing in the stack window. As best I can figure, my xemacs whines before it really gets started. The address associated with it is: 0x6106fb17. stackdump generated after "c"ontinuing past the SIGSERV: Exception: STATUS_ACCESS_VIOLATION at eip=6106FB17 eax=00000004 ebx=610073F6 ecx=00000003 edx=12020D4C esi=610073F2 edi=00000004 ebp=0280F8C8 esp=0280FD64 program=D:\cygwin\usr\local\src\xemacs-21.2.36\src\xemacs.exe cs=001B ds=0023 es=0023 fs=0038 gs=0000 ss=0023 Stack trace: Frame Function Args 0280F8C8 6106FB17 (00000000, 00000000, 00000000, 00000000) 0280FD70 6106FB17 (12020D4C, 610073F2, 00000004, 610078B1) 0280FDA0 610078C8 (610073F2, 0280FDCC, 0280FDD0, 61005FAF) 0280FDD0 6100791A (610073F2, 0A015E40, 0280FE10, 610076CC) 0280FE10 610076E6 (0A015E40, 00000000, 0280FE50, 61023F83) 0280FE50 610077DC (0A013074, 0A015E45, 00000005, 00000000) 0280FEA0 61008773 (00000000, 00000064, 6100D6FD, 610032F4) 0280FEC0 61030E57 (00000000, 00000000, 0280FF10, 610032FC) 0280FF10 6100335A (00000000, 00000208, 00000246, 8052A98F) 0280FF40 610038C5 (0043CA88, 00000208, 85F10020, 00000246) 0280FF60 61003904 (00000000, 00000000, 00780018, 00000002) 0280FF90 00571CD3 (0043CA88, 00000000, 80100000, BF09CD00) 0280FFC0 0040103D (00000208, 0000021A, 7FFDF000, 00000008) 0280FFF0 77E992A6 (00401000, 00000000, 000000C8, 00000100) End of stack trace "Program exited with code 0305400" --Chuck P.S. I do have a perfectly good windows-native-XEmacs -- the only reason I built this cygwin version was to test my libXpm and libncurses stuff, since no one else seems interested. However, it looks like I've stumbled onto some *other* error -- again, cygwin-XEmacs+ncurses+libXpm works like a charm as long as I start it from bash... Oh well, if it's not one thing it's another. -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com