all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Frank Terbeck <ft@bewatermyfriend.org>
Cc: 37671@debbugs.gnu.org
Subject: bug#37671: 27.0.50; Segmentation fault with --fg-daemon on Linux
Date: Sat, 01 Feb 2020 10:46:45 +0200	[thread overview]
Message-ID: <834kwak83u.fsf@gnu.org> (raw)
In-Reply-To: <87ftfvf2ny.fsf@ft.bewatermyfriend.org> (message from Frank Terbeck on Sat, 01 Feb 2020 03:43:13 +0100)

> From: Frank Terbeck <ft@bewatermyfriend.org>
> Cc: 37671@debbugs.gnu.org
> Date: Sat, 01 Feb 2020 03:43:13 +0100
> 
> (gdb) p w->current_matrix
> $12 = (struct glyph_matrix *) 0x7a
> 
> (gdb) p draw
> $13 = DRAW_NORMAL_TEXT
> 
> (gdb) p hlinfo->mouse_face_hidden
> $14 = false
> 
> (gdb) p hlinfo->mouse_face_end_row
> $15 = 16
> 
> (gdb) p w->current_matrix->nrows
> Cannot access memory at address 0x92
> 
> (gdb) p w->current_matrix
> $17 = (struct glyph_matrix *) 0x7a

This window is dead, AFAICT, and its memory has been recycled.  So
somehow we attempt to show mouse highlight on a deleted window or
something.  I have no idea how this could have happened.

Moreover, the frame itself seems to have bogus values:

> (gdb) p *f
> $10 = {header = {size = 285941742698496},
>        name = 0x55573dc812400000,
>        icon_name = 0xfffffffffe000055,
>        title = 0xfffffffffeffffff,
>        parent_frame = 0xfffffffffeffffff,
>        focus_frame = 0xfffffffffeffffff,
>        root_window = 0xfffffffffeffffff,
>        selected_window = 0xfffffffffeffffff,
>        old_selected_window = 0xfffffffffeffffff,
>        minibuffer_window = 0xfffffffffeffffff,
>        param_alist = 0xfffffffffeffffff,
>        scroll_bars = 0xfffffffffeffffff,
>        condemned_scroll_bars = 0xfffffffffeffffff,
>        menu_bar_items = 0xfffffffffeffffff,
>        face_alist = 0xfffffffffeffffff,
>        menu_bar_vector = 0xfffffffffeffffff,
>        buffer_predicate = 0xfffffffffeffffff,
>        buffer_list = 0xfffffffffeffffff,
>        buried_buffer_list = 0xfffffffffeffffff,
>        tab_bar_window = 0xfffffffffeffffff,
>        desired_tab_bar_string = 0xfffffffffeffffff,
>        current_tab_bar_string = 0xfffffffffeffffff,
>        tool_bar_window = 0xfffffffffeffffff,
>        desired_tool_bar_string = 0xfffffffffeffffff,
>        current_tool_bar_string = 0xfffffffffeffffff,
>        font_data = 0xfffffffffeffffff,
>        tab_bar_items = 0xfffffffffeffffff,
>        tool_bar_items = 0xfffffffffeffffff,
>        face_cache = 0xfffffffffeffffff,
>        last_tab_bar_item = -16777217,
>        last_tool_bar_item = -1,
>        menu_bar_items_used = -16777217,
>        namebuf = 0xfffffffffeffffff <error: Cannot access memory at address 0xfffffffffeffffff>,
>        shell_position = 0xfffffffffeffffff <error: Cannot access memory at address 0xfffffffffeffffff>,

What exactly did you do immediately prior to the crash?





  reply	other threads:[~2020-02-01  8:46 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-09  1:55 bug#37671: 27.0.50; Segmentation fault with --fg-daemon on Linux Frank Terbeck
2019-10-10 11:03 ` Eli Zaretskii
2019-10-10 18:27   ` Frank Terbeck
2020-01-08  3:23     ` Frank Terbeck
2020-01-08 16:28       ` Eli Zaretskii
2020-01-08 16:39         ` Frank Terbeck
2020-02-01  2:28           ` Frank Terbeck
2020-02-01  8:33             ` Eli Zaretskii
2020-02-01  2:43           ` Frank Terbeck
2020-02-01  8:46             ` Eli Zaretskii [this message]
2020-02-01 11:28               ` Frank Terbeck
2020-02-01 12:04                 ` Eli Zaretskii
2020-02-01 12:49                   ` Frank Terbeck
2020-02-01 13:08                     ` Eli Zaretskii
2020-02-01 14:32                       ` Frank Terbeck
2020-02-15  8:28                         ` Eli Zaretskii
2020-02-15 11:32                           ` Frank Terbeck
2020-03-05  7:19                             ` Eli Zaretskii
2020-03-06  0:09                               ` Frank Terbeck
2020-03-06  7:51                                 ` Eli Zaretskii
2019-10-10 20:56 ` Paul Eggert
2019-10-11  7:02   ` Eli Zaretskii

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=834kwak83u.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=37671@debbugs.gnu.org \
    --cc=ft@bewatermyfriend.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.