Article View: gnu.epoch.misc
Article #1684epoch 4.01a crash data
From: Dan Mack
Date: Sat, 09 Nov 1991 18:32
Date: Sat, 09 Nov 1991 18:32
70 lines
3394 bytes
3394 bytes
Epoch still seems to have that characteristic of occasionally crashing for no apparent reason. I'm using epoch 4.01a under X11R5 ( no fixes applied yet ) on a Sun 4/470 ( SunOS 4.1.1 ). Here's what gdb said about the core file: (antony) 12:08 ~ ] gdb epoch core GDB is free software and you are welcome to distribute copies of it under certain conditions; type "info copying" to see the conditions. There is absolutely no warranty for GDB; type "info warranty" for details. GDB 4.1, Copyright 1991 Free Software Foundation, Inc... Core file invoked as `epoch'. Program terminated with signal 11, Segmentation fault. #0 0x34d64 in current_column () (gdb) info stack #0 0x34d64 in current_column () #1 0x351a0 in Findent_to () #2 0x484c4 in Ffuncall () #3 0x545d0 in Fbyte_code () #4 0x47b30 in Feval () #5 0x4580c in Fprogn () #6 0x48a30 in funcall_lambda () #7 0x485e8 in Ffuncall () #8 0x545d0 in Fbyte_code () #9 0x47b30 in Feval () #10 0x4580c in Fprogn () #11 0x48a30 in funcall_lambda () #12 0x485e8 in Ffuncall () #13 0x545d0 in Fbyte_code () #14 0x47b30 in Feval () #15 0x4580c in Fprogn () #16 0x48d54 in unbind_to () #17 0x54650 in Fbyte_code () #18 0x47b30 in Feval () #19 0x4580c in Fprogn () #20 0x48a30 in funcall_lambda () #21 0x485e8 in Ffuncall () #22 0x451a8 in Fcall_interactively () #23 0x25cec in Fcommand_execute () #24 0x25f48 in Fexecute_extended_command () #25 0x484a0 in Ffuncall () #26 0x451a8 in Fcall_interactively () #27 0x25cec in Fcommand_execute () #28 0x2436c in command_loop_1 () #29 0x46c70 in internal_condition_case () #30 0x239f4 in command_loop_2 () #31 0x4668c in internal_catch () #32 0x239ac in command_loop () #33 0x235f4 in recursive_edit_1 () #34 0x23588 in Frecursive_edit () -- I wasn't even typing when it crashed this time. Maybe it was garbage collecting, or auto saving when it crashed. I just noticed that the window vanished and sure enough, there was a core file in my home directory. Hope this helps you track down this elusive bug. Almost every epoch user I know has experienced these occasional seg. faults but we still tolerate it since it always has the courtesy to autosave before dying :^). Dan -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Dan Mack mack@umn-cs.umn.edu D The human race was dying out ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ --- T O no one left to scream and shout grad-admin @ sun-admin / | \ H O People walking on the moon University of Minnesota \ /|\ / E R SMOG will get you pretty soon! Computer Science Department --- S Ship of fools, Ship of fools... ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Technical Details
Message-ID:
<MACK.91Nov9123252@janus.cs.umn.edu>Path:
arc1-ca.pugleaf.net!gmdzi!unido!mcsun!uunet!spool.mu.edu!cs.umn.edu!cs.umn.edu!mackShow Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: fc7ee,f76e3880a40db79e,start X-Google-Attributes: gidfc7ee,public X-Google-ArrivalTime: 1991-11-09 10:49:18 PST Path: arc1-ca.pugleaf.net!gmdzi!unido!mcsun!uunet!spool.mu.edu!cs.umn.edu!cs.umn.edu!mack From: mack@janus.cs.umn.edu (Dan Mack) Newsgroups: gnu.epoch.misc Subject: epoch 4.01a crash data Message-ID: <MACK.91Nov9123252@janus.cs.umn.edu> Date: 9 Nov 91 18:32:52 GMT Sender: news@cs.umn.edu (News administrator) Reply-To: mack@cs.umn.edu Distribution: gnu Organization: computer science dept Lines: 70 Nntp-Posting-Host: janus.cs.umn.edu