Thread View: gnu.epoch.misc
2 messages
2 total messages
Started by Mark D. Baushke
Wed, 06 May 1992 17:00
epoch 4.0p1 core dump
Author: Mark D. Baushke
Date: Wed, 06 May 1992 17:00
Date: Wed, 06 May 1992 17:00
109 lines
4872 bytes
4872 bytes
Hardware: Sun-4c/25
OS: SunOS 4.1.1
Epoch: 4.0p1 + gravity fix from Chris Love
X Vers: X11R5p11
While operating an NCD X Terminal over a 19200 dialup using Xremote.
A core dump occured while doing a (set-window-configuration ...) of a
savd (current-window-configuration).
BTW: I have also been seeing screen update problems when doing this
kind of operation. A (recenter) clears the problem up.
-- Mark
Current directory is /home/toolsrc/ndir/sos4/gnu/epoch/src/
GDB is free software and you are welcome to distribute copies of it
under certain conditions; type "show copying" to see the conditions.
There is absolutely no warranty for GDB; type "show warranty" for details.
GDB 4.5, Copyright 1992 Free Software Foundation, Inc...
(gdb) core-file ~/epoch.core
Warning: core file may not match specified executable file.
Core was generated by `epoch'.
Program terminated with signal 6, Abort.
#0 0x81390 in kill ()
(gdb) bt
#0 0x81390 in kill ()
#1 0x870dc in abort ()
#2 0x18474 in layout_window (window=336645128, just_this_one=0)
at xdispepoch.c:1197
#3 0x18160 in layout_windows (window=336645128) at xdispepoch.c:1110
#4 0x17e50 in redisplay_screen (rb=0x123808, force=1) at xdispepoch.c:992
#5 0x17b00 in redisplay () at xdispepoch.c:892
#6 0x23160 in read_command_char (commandflag=1) at keyboard.c:942
#7 0x23f9c in read_key_sequence (keybuf=0xf7fff308 "\030\r", bufsize=30,
prompt=0x0, nodisplay=0) at keyboard.c:1548
#8 0x22b30 in command_loop_1 () at keyboard.c:669
#9 0x44b58 in internal_condition_case (bfun=0x22948 <command_loop_1>,
handlers=17869072, hfun=0x2248c <cmd_error>) at eval.c:1018
#10 0x227c8 in command_loop_2 () at keyboard.c:541
#11 0x44684 in internal_catch (tag=17869052, func=0x227a4 <command_loop_2>,
arg=17868812) at eval.c:826
#12 0x22774 in command_loop () at keyboard.c:523
#13 0x22404 in recursive_edit_1 () at keyboard.c:408
#14 0x22394 in Frecursive_edit () at keyboard.c:390
#15 0x21d64 in main (argc=6, argv=0xf7fff76c, envp=0xf7fff788) at emacs.c:575
(gdb) up
#1 0x870dc in abort ()
(gdb) up
#2 0x18474 in layout_window (window=336645128, just_this_one=0)
at xdispepoch.c:1197
(gdb) info reg
g0 0x0 0
g1 0x25 37
g2 0x8000000 134217728
g3 0x80000 524288
g4 0x8fde4 589284
g5 0x0 0
g6 0x0 0
g7 0x0 0
o0 0xfd800 1038336
o1 0x110a80c 17868812
o2 0x1131ec 1126892
o3 0x1410cd08 336645384
o4 0x0 0
o5 0x96400 615424
sp 0xf7ffef60 -134221984
o7 0x1846c 99436
l0 0x0 0
l1 0x20414 132116
l2 0x10cc08 1100808
l3 0x0 0
l4 0x123908 1194248
l5 0x0 0
l6 0x7 7
l7 0x0 0
i0 0x1410cc08 336645128
i1 0x0 0
i2 0x123808 1193992
i3 0x23cf08 2346760
i4 0x1c20 7200
i5 0x60000000 1610612736
fp 0xf7ffeff8 -134221832
i7 0x18158 98648
y 0x0 0
psr 0x90400085 -1874853755
wim 0x0 0
tbr 0x0 0
pc 0x81390 529296
npc 0x81394 529300
fpsr 0x0 0
cpsr 0x0 0
(gdb) p w
$1 = (struct window *) 0x10cc08
(gdb) p *w
$2 = {size = 35, vec_next = 0x10c408, next = 336645384, prev = 17868812,
hchild = 17868812, vchild = 17868812, parent = 17868812, pixleft = 2,
pixtop = 2, pixwidth = 640, pixheight = 741, lines = 17868812,
modeline = 17868812, size_change = 17868852, buffer = 17868812,
start = 34647076, pointm = 34647088, force_start = 17868812, hscroll = 0,
use_time = 109, sequence_number = 1, temslot = 1, last_modified = 9,
last_point = 1, last_point_x = 0, last_point_y = 0, last_mark_x = 17868812,
last_mark_y = 17868812, window_end_pos = 0, window_end_valid = 17868812,
window_end_vpos = 0, window_end_ppos = 28, update_mode_line = 17868812,
start_at_line_beg = 17868852, root = 370292744, height = 2,
start_button = 17868812}
(gdb) p * w->buffer
Cannot access memory at address 0x110a80c.
(gdb)
Re: epoch 4.0p1 core dump
Author: mthome
Date: Thu, 07 May 1992 05:42
Date: Thu, 07 May 1992 05:42
16 lines
1266 bytes
1266 bytes
Re: >From: "Mark D. Baushke" <mdb@nsd.3com.com> >Subject: epoch 4.0p1 core dump >A core dump occured while doing a (set-window-configuration ...) of a >savd (current-window-configuration). I also had a core-dump like this (just yesterday) - Epoch 4.0p1 (no fixes) X11R5p9 (I think) Sun cc, SunOs 4.1.1 using a Sun3 server (same X11R5). Not the same cause (was not doing a (set-window-configuration)), but whatever happened, it resulted in the same error: layout_window called on a bufferless window. My core is available for examination, but it looks very similar to that in the above mentioned message. cheers, -mik (Michael Thome, mthome@BBN.Com)
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads