Subject: Re: cygwin_except_handler problem !
From: [email-masked] (Geoffrey Noer)

16 Nov 1997 16:02:57 -0800
Message-ID: <[email-masked]>
References: <[email-masked]>
Content-Type: text
To: [email-masked] (Pasa Guglielmo)
Cc: [email-masked]

Pasa Guglielmo wrote:
[...]
> Does anybody know what is this all about and if that kind of problem is
> thought to disappear with a next version of cygwin ?
> 
> gui@JAMES/usr/gnuwin32/b18# xephem
> (D:\USR\X11R6.3\BIN\XEPHEM.EXE 1011) In cygwin_except_handler exc
> C0000005 at 5D
> 266D sp 275E14C
> (D:\USR\X11R6.3\BIN\XEPHEM.EXE 1011) Exception trapped!
> (D:\USR\X11R6.3\BIN\XEPHEM.EXE 1011) exception C0000005 at 5D266D
> (D:\USR\X11R6.3\BIN\XEPHEM.EXE 1011) exception: ax FFFFFFFF bx FFFFFFFF
> cx 53 dx
>  FFFFFFFF
> (D:\USR\X11R6.3\BIN\XEPHEM.EXE 1011) exception: si 275E33C di 2 bp
> 275E150 sp 27
> 5E14C
> (D:\USR\X11R6.3\BIN\XEPHEM.EXE 1011) exception is:
> STATUS_ACCESS_VIOLATION

XEPHEM.EXE had a segmentation violation (STATUS_ACCESS_VIOLATION).
Cygwin did the right thing and trapped the exception but it is probably
not at fault.

The next release changes the output to print something like the following
to the screen:

(D:\USR\X11R6.3\BIN\XEPHEM.EXE 1011) Exception: STATUS_ACCESS_VIOLATION
Dumping strack trace to XEPHEM.EXE.core

-- 
Geoffrey Noer
[email-masked]
-
For help on using this list (especially unsubscribing), send a message to
"[email-masked]" with one line of text: "help".