emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Emacs crashes, 07nov16


From: Jan Djärv
Subject: Re: Emacs crashes, 07nov16
Date: Wed, 21 Nov 2007 08:42:09 +0100
User-agent: Thunderbird 2.0.0.9 (X11/20071031)



Robert J. Chassell skrev:
    It does not look like this backtrace was made with (x-synchronize t)...

Oops!  I forgot.  My apologies.  Here it is again.   It does not look
any better.  What would you like me to try next?


Hmm, it looks like someone is overwriting the stack. 77 is X_ImageText16 (XDrawImageString16) so some parameter to that call is bad. But where that corruption happens is har to know. Try this:

(gdb) l x_draw_glyph_string_foreground
(gdb) l
    <and more l until you see>:

1373              if (s->two_byte_p)
1374                XDrawImageString16 (s->display, s->window, s->gc, x,
1375                                    s->ybase - boff, s->char2b, s->nchars);
1376              else
1377                XDrawImageString (s->display, s->window, s->gc, x,
1378                                  s->ybase - boff, char1b, s->nchars);

    <your line numbers may not be the same>

(gdb) b 1374
    <i.e. the line that XDrawImageString16 is on.  Not to be confused with
     XDrawString16 that occurs a bit before this line>
(gdb) r
    <Try to display the euro char, breakpoint should be hit>
(gdb) p *s
(gdb) p *s->font
(gdb) p *s->font_info
(gdb) p x
(gdb) p boff

No need to use x-synchronize for this.

Another thing you can try is another 20 -point font, like courier.


        Jan D.



(gdb) bt full
#0  x_connection_closed (dpy=0x85b8b80, error_message=0xbfaef5e8 "X protocol error: 
BadValue (integer parameter out of range for operation) on protocol request 77") at 
xterm.c:7786
        dpyinfo = <value optimized out>
        frame = <value optimized out>
        tail = <value optimized out>
#1  0x080cceea in x_error_quitter (display=0x85b8b80, error=0xbfaef89c) at 
xterm.c:7968
        buf = "BadValue (integer parameter out of range for operation)", '\0' 
<repeats 200 times>
        buf1 = "X protocol error: BadValue (integer parameter out of range for operation) on protocol 
request 77\000\000\000\000\n\f\220\2670mZ\b\300\220[\b\210\366\256\277\251\002\220\2670mZ\b\340\366\256\277 
", '\0' <repeats 11 times>, 
"\330\220[\b\214&\034\267$\233\232\267\000\000\000\000\200\213[\b\310\366\256\277\005\r\220\267\200\213[\b\340\366\256\277
 \000\000\000$\233\232\267\000\000\000\000`\331\000\000\350\366\256\277\024A\212\267\200"...
#2  0x080ccf40 in x_error_handler (display=0x85b8b80, error=0xbfaef89c) at 
xterm.c:7924
No locals.
#3  0xb78ff1ef in _XError () from /usr/lib/libX11.so.6
No symbol table info available.
#4  0xb7900dcb in _XReply () from /usr/lib/libX11.so.6
No symbol table info available.
#5  0xb78f80b8 in XSync () from /usr/lib/libX11.so.6
No symbol table info available.
#6  0xb78f8243 in ?? () from /usr/lib/libX11.so.6
No symbol table info available.
#7  0x085b8b80 in ?? ()
No symbol table info available.
#8  0x00000000 in ?? ()
No symbol table info available.
(gdb)

Today's GNU Emacs CVS snapshot, Tue, 2007 Nov 20  11:48 UTC
GNU Emacs 23.0.50.7 (i686-pc-linux-gnu, GTK+ Version 2.12.1)
started in debugger with
    set args -i -q \
    --eval '(emacs-version t)' -bg DodgerBlue4 -fg white \
    -fn '-Misc-Fixed-Medium-R-Normal--20-200-75-75-C-100-ISO8859-1' \
    -geometry 80x44+660+51 -name '-q GNU Emacs in Debugger 4'





reply via email to

[Prev in Thread] Current Thread [Next in Thread]