From: Kaushal Modi <kaushal.modi@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 29031@debbugs.gnu.org
Subject: bug#29031: 25.3; Segmentation fault when starting emacs with my config
Date: Mon, 30 Oct 2017 18:34:22 +0000 [thread overview]
Message-ID: <CAFyQvY17RXss2Fpv+mJm0xgOfcNT41Ko5cmWp=DsRfuOPrGYzA@mail.gmail.com> (raw)
In-Reply-To: <83r2tkts1f.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 3319 bytes --]
>
> So what is the problematic data here? Is 'glyph' a NULL pointer or
> something? Or is 'it' a garbled pointer? What do these commands
> show:
>
> (gdb) p glyph
> (gdb) p glyph->charpos
> (gdb) p it->position
>
This is what I got:
Thread 1 "emacs" received signal SIGSEGV, Segmentation fault.
0x000000000043d101 in append_glyph (it=0x7fffffff2370) at xdisp.c:25880
25880 xdisp.c: No such file or directory.
(gdb) bt
#0 0x000000000043d101 in append_glyph (it=0x7fffffff2370) at xdisp.c:25880
#1 x_produce_glyphs (it=0x7fffffff2370) at xdisp.c:27175
#2 0x0000000000452032 in display_line (it=0x7fffffff2370) at xdisp.c:20676
#3 0x0000000000457868 in try_window (window=18793157, pos=..., flags=1) at
xdisp.c:17251
#4 0x0000000000460e41 in redisplay_window (window=18793157,
just_this_one_p=false)
at xdisp.c:16700
#5 0x0000000000463b36 in redisplay_window_0 (window=<optimized out>) at
xdisp.c:14491
#6 0x000000000055e7c6 in internal_condition_case_1 (bfun=0x463b10
<redisplay_window_0>,
arg=18793157, handlers=<optimized out>, hfun=0x429b40
<redisplay_window_error>)
at eval.c:1339
#7 0x000000000044612e in redisplay_windows (window=<optimized out>) at
xdisp.c:14471
#8 0x000000000045cfd5 in redisplay_internal () at xdisp.c:14031
#9 0x00000000004f5299 in read_char (commandflag=1, map=102809939,
prev_event=0,
used_mouse_menu=0x7fffffffb0ff, end_time=0x0) at keyboard.c:2482
#10 0x00000000004f90c0 in read_key_sequence (keybuf=0x7fffffffb170,
prompt=0,
dont_downcase_last=false, can_return_switch_frame=true,
fix_current_buffer=true,
prevent_redisplay=false, bufsize=30) at keyboard.c:9068
#11 0x00000000004fa3ba in command_loop_1 () at keyboard.c:1370
#12 0x000000000055e82a in internal_condition_case (bfun=0x4fa1f0
<command_loop_1>,
handlers=<optimized out>, hfun=0x4f8200 <cmd_error>) at eval.c:1315
#13 0x00000000004f81ec in command_loop_2 (ignore=<optimized out>) at
keyboard.c:1112
#14 0x000000000055e8b8 in internal_catch (tag=<optimized out>,
func=0x4f81d0 <command_loop_2>, arg=0) at eval.c:1080
#15 0x00000000004f7f67 in command_loop () at keyboard.c:1091
#16 0x00000000004f7ff5 in recursive_edit_1 () at keyboard.c:697
#17 0x00000000004f8135 in Frecursive_edit () at keyboard.c:768
#18 0x00000000004e997e in main (argc=<optimized out>, argv=<optimized out>)
at emacs.c:1629
(gdb) p glyph
$1 = (struct glyph *) 0x8f
(gdb) p glyph->charpos
Cannot access memory at address 0x8f
(gdb) p it->position
$2 = {charpos = 1, bytepos = 1}
(gdb)
Basically, I need you to run this under a debugger and answer several
> questions. Bonus points for reproducing this in an unoptimized build
> configured with --enable-checking='yes,glyphs', and then showing the
> backtrace from the segfault.
>
> IOW, this problem needs to be debugged, and for that we need data that
> explains the crash. Could you please help in collecting that data?
>
Sure.
Another data point: I can prevent the crash if I add nlinum-enabling hooks
in window-setup-hook instead of after-init-hook. When using emacsclient
(daemon), I do that nlinum enabling in after-make-frame-functions. So I see
this crash only when running emacs (not emacsclient), on 25.3.
Let me try to build emacs-25 branch with your suggested options.. hopefully
I can recreate the crash on that.
--
Kaushal Modi
[-- Attachment #2: Type: text/html, Size: 4428 bytes --]
next prev parent reply other threads:[~2017-10-30 18:34 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-27 21:24 bug#29031: 25.3; Segmentation fault when starting emacs with my config Kaushal Modi
2017-10-30 14:17 ` Kaushal Modi
2017-10-30 16:03 ` Kaushal Modi
2017-10-30 18:37 ` Eli Zaretskii
2017-10-30 19:24 ` Kaushal Modi
2017-10-30 19:34 ` Eli Zaretskii
2017-10-30 19:51 ` Eli Zaretskii
2017-10-30 21:36 ` Kaushal Modi
2017-10-31 20:26 ` Eli Zaretskii
2017-10-31 20:52 ` Kaushal Modi
2017-10-31 20:56 ` Eli Zaretskii
2017-11-07 13:27 ` Noam Postavsky
2017-11-07 13:30 ` Kaushal Modi
2017-11-07 13:55 ` Noam Postavsky
2017-10-30 18:22 ` Eli Zaretskii
2017-10-30 18:34 ` Kaushal Modi [this message]
2017-10-30 18:52 ` Eli Zaretskii
2017-10-30 18:57 ` Kaushal Modi
2017-10-30 19:18 ` Kaushal Modi
2017-10-30 19:28 ` Eli Zaretskii
2019-09-29 0:44 ` Stefan Kangas
2019-09-29 0:58 ` Noam Postavsky
2019-09-29 7:26 ` Eli Zaretskii
2019-10-30 20:17 ` Stefan Kangas
2019-10-30 20:47 ` Kaushal Modi
2019-10-30 21:16 ` Stefan Kangas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAFyQvY17RXss2Fpv+mJm0xgOfcNT41Ko5cmWp=DsRfuOPrGYzA@mail.gmail.com' \
--to=kaushal.modi@gmail.com \
--cc=29031@debbugs.gnu.org \
--cc=eliz@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.