xclearcase bug

[Adrian Aichner]

Malakasis Spiros <spma at intracom.gr> writes:

Hi Malakasis, what makes this an xclearcase bug?

- What happened.
- What you thought should have happened.
- Precisely what you were doing at the time.

M-x report-xemacs-bug
will ask you these exact questions.

Best regards,

Adrian

> Operating System:SunOS Release 5.8 Generic_108528-15
> Desktop:CDE 1.4.7,X11 Version 6.4.1
> Workstation Type:SUNW,Sun-Blade-150;sparc;sun4u
>
>
>
> Fatal error (4).
> Your files have been auto-saved.
> Use `M-x recover-session' to recover them.
>
> Please report this bug to the address `crashes at xemacs.org'.
> *MAKE SURE* to include as much configuration information as
> possible; at the very least what OS and hardware you are running
> on, and hopefully also what compiler and compiler options the
> binary was compiled with, what options XEmacs was compiled with,
> whether you are using a prebuilt binary from ftp.xemacs.org or
> compiled XEmacs yourself for your system, etc.
>
> If at all possible, *please* try to obtain a C stack backtrace;
> it will help us immensely in determining what went wrong.
> To do this, locate the core file that was produced as a result
> of this crash (it's usually called `core' and is located in the
> directory in which you started XEmacs, or maybe in your home
> directory), and type
>
>   gdb /tools/vws/bin/xemacs core
>
> then type `where' when the debugger prompt comes up.
> (If you don't have GDB on your system, you might have DBX,
> or XDB, or SDB.  A similar procedure should work for all of
> these.  Ask your system administrator if you need more help.)
>
> Lisp backtrace follows:
>
>   # (condition-case ... . error)
>   # (catch top-level ...)
>
> C backtrace follows:
> (A real debugger may provide better information)
>
> 18266: /tools/vws/bin/xemacs
> /view/spma__BBMS1.8.2__prs3880/home/projects/ads
>  fed9c2c8 waitid   (0, 4784, ffbece30, 103)
>  fed563a8 _waitpid (0, ffbecf1c, 100, ffbecf1c, 215f8, fed9184c) + 60
>  fed91860 system   (ffbed104, 178b94, 178b30, 475a, 0, 6b974) + 264
>  00068298 fatal_error_signal (178b30, 267c00, 273c00, fedb801c, 0, 0) +
> d4
>  fed9b4d0 sigacthandler (4, 0, ffbed238, ff072000, 4, 8) + 28
>  --- called from signal handler with signal 4 (SIGILL) ---
>  00479728 ???????? (70, 0, 46, 4796cc, 4796c0, 5a2c00)
>  001362b4 call_callbacks (5a2c00, 5, 390c774a, 0, 0, 12c00176) + b4
>  00138854 timer    (5, ffbed6f0, 138750, 5a2c00, 2cf000, ffbed6f4) + 104
>
>  ff040678 XtAppProcessEvent (2f5800, 1, 102a2004, 0, 4, 2) + 218
>  001080c8 emacs_Xt_next_event (482744, 273f2c, 273c00, 2a2004, 2a2004,
> fffffff) + 140
>  00075d98 event_stream_next_event (10482744, 271c00, 2a2004, fffffff, 0,
> 6abb) + 54
>  00077920 next_event_internal (482744, 1, 272800, fffffff, 0, 0) + b4
>  00077d58 Fnext_event (102a2004, 1a284c, 273f2c, ffffc00, 0, 2e5bc0) +
> 350
>  00055f54 Fcommand_loop_1 (26dc00, 273c00, 0, fffffff, 267c00, 0) + 1d8
>  0006bad4 condition_case_1 (267c00, 275000, 272800, 5571c, 102a2004, 0)
> + 110
>  00055808 command_loop_3 (27b000, 273f2c, 55400, 55c00, 102a2004, 0) +
> 28
>  00055830 command_loop_2 (102a2004, 5582c, 0, 0, 0, 0) + 4
>  0006b734 internal_catch (102b4ef4, 5582c, 102a2004, 0, 1a0928, 0) + ac
>  00055a30 initial_command_loop (271d50, 273f2c, fffffff, 26d800, 178c44,
> 2d) + 1e8
>  000690dc main_1   (273c00, ffbedd3c, 102a2004, 271c00, 29c800, 0) + b98
>
>  000694d8 main     (0, 0, 0, 0, 0, 0) + a4
> Illegal Instruction - core dumped
>
>
>

-- 
Adrian Aichner
 mailto:adrian at xemacs.org
 http://www.xemacs.org/