From: Gregor Zattler via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: "Pip Cet" <pipcet@protonmail.com>,
"Gerd Möllmann" <gerd.moellmann@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, 75459@debbugs.gnu.org
Subject: bug#75459: 31.0.50; scratch-igc: Breakpoint 1, terminate_due_to_signal (sig=sig@entry=6, backtrace_limit=backtrace_limit@entry=2147483647) at ./src/emacs.c:432
Date: Thu, 09 Jan 2025 23:29:07 +0100 [thread overview]
Message-ID: <87tta7sjt8.fsf@no.lan> (raw)
In-Reply-To: <87plkv3hzd.fsf@protonmail.com>
Hi Pip,
* Pip Cet <pipcet@protonmail.com> [2025-01-09; 19:27 GMT]:
[... 29 Zeilen deleted ...]
> "deadl", which appears at the beginning of an Emacs string ("deadline") only in
> org-agenda.el. The string is unlikely to start earlier because the next
> byte would be 0x08, an ASCII backspace. Unlikely.
>
> More likely it's an unaligned string. I think Emacs string data is
> always aligned, except for pure strings. But on scratch/igc, even pure
> strings are aligned to an 8-byte boundary!
>
> "closed" also appears in org-agenda.el, but this string isn't
> NUL-terminated: it's a Pascal-style string, with a length byte (0x06)
> followed by 6 ASCII characters. That would match the 8-byte "deadline"
> literal.
>
> Possibly a (basic) compression format, probably lz4 or zlib. I'm
> guessing this is a git object, which is stored in zlib format, and that
> appears to use length-prefixed string literals like these.
>
> What is it doing in your Emacs data?
I have no idea. If I remember
correctly, I started Emacs and told it
to load the org-agenda files, and that
would be it, these are plain text.
I do every day at least once. This did
not happen before. I tried to reproduce
in an Emacs optimized for debugging, but
the problem did not occur.
[... 392 Zeilen deleted ...]
> Can you try "p $rsp"?
(gdb) p $rs
$7 = void
Upps, "rs" != "rsp"
(gdb) p $rsp
$10 = (void *) 0x7fffffff95f8
Ciao; Gregor
next prev parent reply other threads:[~2025-01-09 22:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-09 11:19 bug#75459: 31.0.50; scratch-igc: Breakpoint 1, terminate_due_to_signal (sig=sig@entry=6, backtrace_limit=backtrace_limit@entry=2147483647) at ./src/emacs.c:432 Gregor Zattler via Bug reports for GNU Emacs, the Swiss army knife of text editors
2025-01-09 13:03 ` Eli Zaretskii
2025-01-09 14:34 ` Gerd Möllmann
2025-01-09 14:47 ` Pip Cet via Bug reports for GNU Emacs, the Swiss army knife of text editors
2025-01-09 15:32 ` Gregor Zattler via Bug reports for GNU Emacs, the Swiss army knife of text editors
2025-01-09 16:14 ` Gerd Möllmann
2025-01-09 19:27 ` Pip Cet via Bug reports for GNU Emacs, the Swiss army knife of text editors
2025-01-09 22:29 ` Gregor Zattler via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2025-01-10 4:52 ` Gerd Möllmann
2025-01-09 14:52 ` Gerd Möllmann
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=87tta7sjt8.fsf@no.lan \
--to=bug-gnu-emacs@gnu.org \
--cc=75459@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=gerd.moellmann@gmail.com \
--cc=pipcet@protonmail.com \
--cc=telegraph@gmx.net \
/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).