Re: SIGABRT while stress-testing with gnuclient/gnudoit

[Alex Schroeder]

One last bit of info -- again the abort happens in the SELECTED_FRAME
macro, so I really assume that I am seing the same abort.  Just making
sure.  ;)

Alex.

New, just happened:

Program received signal SIGABRT, Aborted.
0x4030b781 in kill () from /lib/libc.so.6
(gdb) l
716       extern int errno;
717     #endif
718     #ifdef HAVE_SETRLIMIT
719       struct rlimit rlim;
720     #endif
721       int no_loadup = 0;
722
723     #if GC_MARK_STACK
724       extern Lisp_Object *stack_base;
725       stack_base = &dummy;
(gdb) bt
#0  0x4030b781 in kill () from /lib/libc.so.6
#1  0x080ce94e in abort () at emacs.c:387
#2  0x08076846 in window_loop (type=GET_BUFFER_WINDOW, obj=1210793848, mini=1, 
frames=405209228) at window.c:1776
#3  0x08076cd4 in Fget_buffer_window (buffer=1210793848, frame=405209228) at 
window.c:1997
#4  0x080623cf in message_dolog (m=0xbfffef28 "n\306'H\\\361\377\277-*\023\bn", 
nbytes=1, nlflag=0, multibyte=1) at xdisp.c:5783
#5  0x0812f7ba in printchar (ch=110, fun=405209228) at print.c:343
#6  0x08132a2d in print_object (obj=405209180, printcharfun=405209228, 
escapeflag=1) at print.c:1532
#7  0x08132021 in print (obj=405209180, printcharfun=405209228, escapeflag=1) 
at print.c:1180
#8  0x08130e4a in Fprin1 (object=405209180, printcharfun=405209180) at 
print.c:731
#9  0x08123ced in Ffuncall (nargs=2, args=0xbffff254) at eval.c:2662
#10 0x0814a34c in Fbyte_code (bytestr=941751892, vector=1210187588, 
maxdepth=10) at bytecode.c:716
#11 0x08124297 in funcall_lambda (fun=1210187312, nargs=1, 
arg_vector=0xbffff388) at eval.c:2851
#12 0x08123e01 in Ffuncall (nargs=2, args=0xbffff384) at eval.c:2716
#13 0x0814a34c in Fbyte_code (bytestr=941752452, vector=1210187964, maxdepth=4) 
at bytecode.c:716
#14 0x08124297 in funcall_lambda (fun=1210187868, nargs=1, 
arg_vector=0xbffff4d8) at eval.c:2851
#15 0x08123e01 in Ffuncall (nargs=2, args=0xbffff4d4) at eval.c:2716
#16 0x081209a9 in Fcall_interactively (function=405517980, 
record_flag=405209180, keys=1210574296) at callint.c:797
#17 0x080daa6a in Fcommand_execute (cmd=405517980, record_flag=405209180, 
keys=405209180, special=405209180) at keyboard.c:9232
#18 0x080d1bd0 in command_loop_1 () at keyboard.c:1644
#19 0x08122249 in internal_condition_case (bfun=0x80d1090 <command_loop_1>, 
handlers=405305524, hfun=0x80d0cd4 <cmd_error>) at eval.c:1267
#20 0x080d0f68 in command_loop_2 () at keyboard.c:1245
#21 0x08121ddd in internal_catch (tag=405267108, func=0x80d0f44 
<command_loop_2>, arg=405209180) at eval.c:1030
#22 0x080d0f17 in command_loop () at keyboard.c:1224
#23 0x080d0a91 in recursive_edit_1 () at keyboard.c:950
#24 0x080d0bc0 in Frecursive_edit () at keyboard.c:1006
#25 0x080cfaef in main (argc=3, argv=0xbffffc54, envp=0xbffffc64) at 
emacs.c:1547
(gdb) up
#1  0x080ce94e in abort () at emacs.c:387
387       kill (getpid (), SIGABRT);
(gdb) up
#2  0x08076846 in window_loop (type=GET_BUFFER_WINDOW, obj=1210793848, mini=1, 
frames=405209228) at window.c:1776
1776        window = FRAME_SELECTED_WINDOW (SELECTED_FRAME ());

Old, which I reported in my first mail:

> Program received signal SIGABRT, Aborted.
> 0x4030b781 in kill () from /lib/libc.so.6
> (gdb) bt
> #0  0x4030b781 in kill () from /lib/libc.so.6
> #1  0x080ce94e in abort () at emacs.c:387
> #2  0x08062aaa in message_with_string (m=0x8174dbe "%s(y or n) ", 
> string=954459916, log=0) at xdisp.c:6054
> #3  0x0812bc9a in Fy_or_n_p (prompt=954459916) at fns.c:2851
> #4  0x08123cda in Ffuncall (nargs=2, args=0xbffff3e4) at eval.c:2659
> #5  0x0814a34c in Fbyte_code (bytestr=956141884, vector=1224197824, 
> maxdepth=6) at bytecode.c:716
> #6  0x08124297 in funcall_lambda (fun=1223704296, nargs=0, 
> arg_vector=0xbffff57c) at eval.c:2851
> #7  0x08123e01 in Ffuncall (nargs=1, args=0xbffff578) at eval.c:2716
> #8  0x0812389f in run_hook_with_args (nargs=1, args=0xbffff578, 
> cond=to_completion) at eval.c:2330
> #9  0x0812371b in Frun_hooks (nargs=1, args=0xbffff608) at eval.c:2198
> #10 0x08123c46 in Ffuncall (nargs=2, args=0xbffff604) at eval.c:2640
> #11 0x08123a27 in call1 (fn=405329060, arg1=405366228) at eval.c:2456
> #12 0x080cfefc in Fkill_emacs (arg=405209180) at emacs.c:1812
> #13 0x080d11f4 in command_loop_1 () at keyboard.c:1369
> #14 0x08122249 in internal_condition_case (bfun=0x80d1090 <command_loop_1>, 
> handlers=405305524, hfun=0x80d0cd4 <cmd_error>) at eval.c:1267
> #15 0x080d0f68 in command_loop_2 () at keyboard.c:1245
> #16 0x08121ddd in internal_catch (tag=405267108, func=0x80d0f44 
> <command_loop_2>, arg=405209180) at eval.c:1030
> #17 0x080d0f17 in command_loop () at keyboard.c:1224
> #18 0x080d0a91 in recursive_edit_1 () at keyboard.c:950
> #19 0x080d0bc0 in Frecursive_edit () at keyboard.c:1006
> #20 0x080cfaef in main (argc=3, argv=0xbffffc54, envp=0xbffffc64) at 
> emacs.c:1547
>
> The new server-edit was going to call find-file, and then raise-frame.
> I am using the ratpoison window manager.  So selected-frame related
> problems sound plausible:
>
> (gdb) up  
> #1  0x080ce94e in abort () at emacs.c:387
> 387       kill (getpid (), SIGABRT);
> (gdb) up
> #2  0x08062aaa in message_with_string (m=0x8174dbe "%s(y or n) ", 
> string=954459916, log=0) at xdisp.c:6054
> 6054          struct frame *f, *sf = SELECTED_FRAME ();
> (gdb) l
> 6049        {
> 6050          /* The frame whose minibuffer we're going to display the 
> message on.
> 6051             It may be larger than the selected frame, so we need
> 6052             to use its buffer, not the selected frame's buffer.  */
> 6053          Lisp_Object mini_window;
> 6054          struct frame *f, *sf = SELECTED_FRAME ();
> 6055
> 6056          /* Get the frame containing the minibuffer
> 6057             that the selected frame is using.  */
> 6058          mini_window = FRAME_MINIBUF_WINDOW (sf);