unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Po Lu <luangruo@yahoo.com>, 52141@debbugs.gnu.org
Subject: bug#52141: 29.0.50; Crash during redisplay
Date: Sat, 27 Nov 2021 16:59:16 +0100	[thread overview]
Message-ID: <m1y259si7f.fsf@yahoo.es> (raw)
In-Reply-To: <83lf19zv5s.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 27 Nov 2021 13:37:35 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

>> 
>> Its type is Lisp_Cons.  However, its address is invalid.  Running
>> `xcons' in gdb complains:
>> 
>> (gdb) xcons
>> $9 = (struct Lisp_Cons *) 0x1e753d0
>> Cannot access memory at address 0x1e753d0
>
> Hmm... and the address is very different from the one which caused the
> segfault.  Strange.
>
> Any ideas, anyone?

Is it possible to run that Emacs instance with some kind of memory
sanitizer enabled (ASAN, Valgrind...)?  That may help catch the
potential memory corruption at the point it happens, not at the point
the garbage collector wants to free it.





  parent reply	other threads:[~2021-11-27 15:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87o865c13p.fsf.ref@yahoo.com>
2021-11-27 11:03 ` bug#52141: 29.0.50; Crash during redisplay Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-27 11:20   ` Eli Zaretskii
2021-11-27 11:32     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-27 11:37       ` Eli Zaretskii
2021-11-27 12:01         ` Andreas Schwab
2021-11-27 15:59         ` Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2021-11-27 16:56           ` Eli Zaretskii
2021-11-28  0:43           ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m1y259si7f.fsf@yahoo.es \
    --to=bug-gnu-emacs@gnu.org \
    --cc=52141@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=luangruo@yahoo.com \
    --cc=mardani29@yahoo.es \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).