This is the mail archive of the mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: XEmacs on cygwin wierdness

On Mon, Nov 13, 2000 at 12:56:12AM -0500, Charles S. Wilson wrote:
>Christopher Faylor wrote:
>>On Mon, Nov 13, 2000 at 12:07:21AM -0500, Charles S.  Wilson wrote:
>>>I've tried to build XEmacs-21.2.36 multiple times tonight.  Each time,
>>>it works perfectly as long as I launch it from with a cygwin-bash
>>>window.  However, if I launch it from the DOS cmd prompt, it
>>Why aren't you running it under gdb to pinpoint where the error is
>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?

>unfortunately, I can't get further than that -- I think it's because of
>the odd structure of an xemacs executable -- in-built lisp data +
>interpreter, this wierd "dumping" process it does to itself when
>building, etc...
>Now, maybe I'm blowing bull patties, but I can't even get the source
>window to show anything but assembler -- because "xemacs.exe" is a
>dumped executable generated by "temacs.exe" which loads a bunch of lisp
>code and data and then "dumps" an image of itself to disk during the
>So, gdb shows *me* nothing -- which is why I asked if anyone could make
>a *guess* as to why a program will run fine under a bash shell, but
>stackdump when run from a DOS box (or within gdb).

Try using gdb -nw.


Want to unsubscribe from this list?
Send a message to

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]