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

Christopher Faylor wrote:
> The more I think about this, the more I think that your stack trace
> should actually be impossible.  It looks like a pointer that should be
> zero isn't.  Out of curiousity, does the patch below cause any
> difference?

Yes, that fixes it.  Now I can run xemacs (without recompiling *it*)
from cmd.exe or from bash.  No problems. However, obviously there is
something wacky going on with xemacs; unfortunately, I don't understand
the wacky structure of xemacs.exe well enough to debug it

I'll give it a shot and report back....

> It shouldn't be necessary but it almost looks like a DLL is being
> invoked with its own 'environ' variable.  Cygwin tries to notice this
> now and tries to synchronize multiple environ's.  However, if the
> DLL initialized the 'environ' prior to cygwin seeing it, that
> could cause problems.
> It probably will have no effect, but could you try the patch?
> This is against my modified version of cygwin so there will be
> some skew when you apply it but it should still apply cleanly.
> If not, you should be able to hand patch it.
> cgf
> Index:
> ===================================================================
> RCS file: /cvs/src/src/winsup/cygwin/,v
> retrieving revision 1.78
> diff -u -p -r1.78
> ---    2000/11/11 05:36:34     1.78
> +++    2000/11/14 03:54:41
> @@ -879,6 +880,7 @@ _dll_crt0 ()
>  #endif
>    main_environ = user_data->envptr;
> +  *main_environ = NULL;
>    user_data->heapbase = user_data->heapptr = user_data->heaptop = NULL;
>    set_console_handler ();
> --
> Want to unsubscribe from this list?
> Send a message to

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]