[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: The very latest emacs (25.1.50) segfault
From: |
Eli Zaretskii |
Subject: |
Re: The very latest emacs (25.1.50) segfault |
Date: |
Mon, 11 Jan 2016 05:39:20 +0200 |
> Date: Mon, 11 Jan 2016 10:24:44 +0900
> From: Masaru Nomiya <address@hidden>
>
> > Can you use the procedure described in the node "Crashing" of the
> > Emacs User manual to produce human-readable backtrace with file names
> > and line numbers out of this? Otherwise it's impossible for us to
> > interpret this data.
>
> Sorry, but I tried.
>
> address@hidden:/tmp/tes/emacs> src/emacs
> Fatal error 11: Segmentation fault
> Backtrace:
> src/emacs[0x4fb622]
> src/emacs[0x4e3384]
> src/emacs[0x4fa52e]
> src/emacs[0x4fa733]
> src/emacs[0x4fa76a]
> /lib64/libpthread.so.0(+0xf1f0)[0x7fc21d1481f0]
> src/emacs[0x5aeda9]
> [...]
>
> (gdb) list *0x5aeda9
> 0x5aeda9 is in ftfont_shape (lisp.h:856).
> 851 }
> 852
> 853 INLINE EMACS_INT
> 854 (XINT) (Lisp_Object a)
> 855 {
> 856 return lisp_h_XINT (a);
> 857 }
> 858
> 859 INLINE EMACS_INT
> 860 (XFASTINT) (Lisp_Object a)
> (gdb)
>
> Is this right?
Yes, but I meant the addr2line method described there. It should
produce more information.
Thanks.
- The very latest emacs (25.1.50) segfault, Masaru Nomiya, 2016/01/10
- Re: The very latest emacs (25.1.50) segfault, Eli Zaretskii, 2016/01/10
- Re: The very latest emacs (25.1.50) segfault, Masaru Nomiya, 2016/01/10
- Re: The very latest emacs (25.1.50) segfault,
Eli Zaretskii <=
- Re: The very latest emacs (25.1.50) segfault, Masaru Nomiya, 2016/01/10
- Re: The very latest emacs (25.1.50) segfault, Masaru Nomiya, 2016/01/11
- Re: The very latest emacs (25.1.50) segfault, Eli Zaretskii, 2016/01/11
- Re: The very latest emacs (25.1.50) segfault, 野宮 賢 / NOMIYA Masaru, 2016/01/12
- Re: The very latest emacs (25.1.50) segfault, K. Handa, 2016/01/12