From: Stefan Kangas <stefan@marxist.se>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 18668-done@debbugs.gnu.org
Subject: bug#18668: 24.3.94; Assertion violation in add_text_properties_1
Date: Wed, 12 Aug 2020 10:06:16 -0700 [thread overview]
Message-ID: <CADwFkmko=__mVXXO-3Rknw9rbF0SfKyktpibbVzTPX3zDCWFOQ@mail.gmail.com> (raw)
In-Reply-To: <874l0iyafw.fsf@gnus.org> (Lars Ingebrigtsen's message of "Wed, 09 Oct 2019 03:28:03 +0200")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Eli Zaretskii <eliz@gnu.org> writes:
>
>> I was editing a C source file, when Emacs 24.3.94 hit an assertion
>> violation. Here's the backtrace and some data:
>>
>> Breakpoint 1, terminate_due_to_signal (sig=sig@entry=22,
>> backtrace_limit=backtrace_limit@entry=2147483647) at emacs.c:350
>> 350 {
>> (gdb) up
>> #1 0x0117096e in die (
>> msg=msg@entry=0x14bf05a <modifier_len+2186> "modified",
>> file=file@entry=0x14bef95 <modifier_len+1989> "textprop.c",
>> line=line@entry=1259) at alloc.c:6833
>> 6833 terminate_due_to_signal (SIGABRT, INT_MAX);
>> (gdb)
>> #2 0x012044f0 in add_text_properties_1 (start=start@entry=310800,
>> end=end@entry=310804, properties=<optimized out>,
>> properties@entry=139616918, object=76471301, object@entry=66533410,
>> set_type=set_type@entry=TEXT_PROPERTY_REPLACE) at textprop.c:1259
>> 1259 eassert (modified);
>
> This was in 2014 -- have you seen this problem since?
More information was requested, but none was given within 44 weeks, so
I'm closing this bug. If this is still an issue, please reply to this
email (use "Reply to all" in your email client) and we can reopen the
bug report.
Best regards,
Stefan Kangas
prev parent reply other threads:[~2020-08-12 17:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-09 13:58 bug#18668: 24.3.94; Assertion violation in add_text_properties_1 Eli Zaretskii
2019-10-09 1:28 ` Lars Ingebrigtsen
2020-08-12 17:06 ` Stefan Kangas [this message]
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='CADwFkmko=__mVXXO-3Rknw9rbF0SfKyktpibbVzTPX3zDCWFOQ@mail.gmail.com' \
--to=stefan@marxist.se \
--cc=18668-done@debbugs.gnu.org \
--cc=larsi@gnus.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.