all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: 54859@debbugs.gnu.org
Subject: bug#54859: Crash in marking of input events with devices
Date: Tue, 12 Apr 2022 08:00:37 +0800	[thread overview]
Message-ID: <87pmlnxja2.fsf@yahoo.com> (raw)
In-Reply-To: <92678974-2fa2-db44-8ae3-69fbb8265168@gmx.at> (martin rudalics's message of "Mon, 11 Apr 2022 18:50:07 +0200")

martin rudalics <rudalics@gmx.at> writes:

> commit c4921d1157a2e3e15b1d779a6bdf768e307275dd
> Author: Po Lu <luangruo@yahoo.com>
> Date:   Fri Apr 8 17:00:37 2022 +0800
>
>     Fix GC marking of input events with devices
>
>     * src/keyboard.c (mark_kboards):
>     * src/pgtkterm.c (mark_pgtkterm): Mark `device' as well.
>
> reliably segfaults my patched version of Emacs.  Note that the line
> numbers of backtraces are not those of master since I have made local
> changes to many of the involved files.  I have not tried to reproduce
> the crashes on master itself because the program to produce the crashes
> uses too many constructs that are not available on master.
>
> A typical crash produced the backtrace below in an -Og -g3 build (-O0
> builds hardly crash that way, if ever).  Note that in my keyboard.c line
> 13102 actually is
>
> 	  mark_object (event->ie.device);
>
> The associated event is always a HELP_EVENT.  If you need further
> information, please tell me.

That was fixed a while back, would you please try with a newer revision?

The problem was that the code to store help events didn't call
EVENT_INIT, so device was left uninitialised.

Thanks.





  reply	other threads:[~2022-04-12  0:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-11 16:50 bug#54859: Crash in marking of input events with devices martin rudalics
2022-04-12  0:00 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-04-12  7:43   ` martin rudalics

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=87pmlnxja2.fsf@yahoo.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=54859@debbugs.gnu.org \
    --cc=luangruo@yahoo.com \
    --cc=rudalics@gmx.at \
    /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.