unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Jonathan Mitchell <mitchell.jkyle@gmail.com>
Cc: 56527@debbugs.gnu.org
Subject: bug#56527: 28.1; Crash on macOS with magit
Date: Thu, 14 Jul 2022 10:11:52 +0300	[thread overview]
Message-ID: <83v8s0tbgn.fsf@gnu.org> (raw)
In-Reply-To: <CAAnK0TYJScxSZ5D6u2gBsXSY18TZ8K9VnAmP6fuUFfmMDBkrTg@mail.gmail.com> (message from Jonathan Mitchell on Thu, 14 Jul 2022 01:11:27 -0500)

> From: Jonathan Mitchell <mitchell.jkyle@gmail.com>
> Date: Thu, 14 Jul 2022 01:11:27 -0500
> Cc: 56527@debbugs.gnu.org
> 
> I think I've worked out how to print basic values in LLDB. The
> vector=0x0000000102931240 appears to be a Marker object in the buffer
> "magit-log: emacs". Both the marker and buffer are printed in the
> attached debugger log.

Thanks.

> (lldb) p *(struct Lisp_Marker *) 0x0000000102931240
> (struct Lisp_Marker) $1248 = {
>   header = (size = 4611686018477740032)
>   buffer = 0x0000000131008600
>   need_adjustment = false
>   insertion_type = false
>   next = nullptr
>   charpos = 1
>   bytepos = 1

So the problem happens because sweep_buffer doesn't set the marker's
buffer to NULL, which is supposed to happen in unchain_dead_markers,
called by sweep_buffers.  The question is why.





  reply	other threads:[~2022-07-14  7:11 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-12 23:27 bug#56527: 28.1; Crash on macOS with magit Jonathan Mitchell
2022-07-13 11:24 ` Eli Zaretskii
2022-07-13 22:16   ` Jonathan Mitchell
2022-07-14  5:20     ` Eli Zaretskii
2022-07-14  6:11       ` Jonathan Mitchell
2022-07-14  7:11         ` Eli Zaretskii [this message]
2022-07-14 15:21           ` Jonathan Mitchell
2022-07-14 16:12             ` Eli Zaretskii
2022-07-14 16:18               ` Jonathan Mitchell
2022-07-14 16:51                 ` Eli Zaretskii
2022-07-14 18:42                   ` Jonathan Mitchell
2022-07-14 19:09                     ` Eli Zaretskii
2022-07-16  8:13                       ` Gerd Möllmann
2022-07-16  8:30                         ` Eli Zaretskii
2022-07-17 15:41                           ` Jonathan Mitchell
2022-07-17 16:03                             ` Eli Zaretskii
2022-07-17 17:19                               ` Jonathan Mitchell
2022-07-17 17:41                                 ` Eli Zaretskii
2022-07-17 17:36                             ` Gerd Möllmann
2022-07-17 18:20                               ` Eli Zaretskii
2022-07-17 20:25                                 ` Alan Third
2022-07-18 12:34                                   ` Eli Zaretskii
2022-07-19 10:44                                     ` Lars Ingebrigtsen
2022-07-19 13:05                                       ` Eli Zaretskii
2022-07-19 19:12                                         ` Jonathan Mitchell
2022-07-19 19:14                                           ` Eli Zaretskii
2022-08-19 12:08                                             ` Lars Ingebrigtsen

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=83v8s0tbgn.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=56527@debbugs.gnu.org \
    --cc=mitchell.jkyle@gmail.com \
    /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).