Subject: Re: bug#18668: 24.3.94; Assertion violation in add_text_properties_1
From: Stefan Kangas <[email-masked]>
To: Lars Ingebrigtsen <[email-masked]>
Cc: Eli Zaretskii <[email-masked]>, [email-masked]
Date: Wed, 12 Aug 2020 10:06:16 -0700
List-Id: <debbugs-submit.debbugs.gnu.org>

Lars Ingebrigtsen <[email-masked]> writes:

> Eli Zaretskii <[email-masked]> 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