all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Richard Stallman <rms@gnu.org>
Cc: 16311@debbugs.gnu.org
Subject: bug#16311: 24.3.50; Crash in next_interval
Date: Wed, 14 Aug 2019 19:04:30 -0700	[thread overview]
Message-ID: <87pnl76v69.fsf@mouse.gnus.org> (raw)
In-Reply-To: <E1Vy9KX-0005YV-G2@fencepost.gnu.org> (Richard Stallman's message of "Tue, 31 Dec 2013 19:06:37 -0500")

Richard Stallman <rms@gnu.org> writes:

> I saved this backtrace since I was running Emacs under GDB.
> I then had to restart Emacs, and I don't recall what triggered it.
>
> #0  0x007cd888 in next_interval (interval=0xf51da884) at intervals.c:728
> #1  0x007d8fa0 in Fnext_single_property_change (position=4, prop=11299786, 
>     object=1959598069, limit=2004) at textprop.c:1053
> #2  0x007e18bc in find_composition (pos=1, limit=501, start=0x7fff0004, 
>     end=0x7fff0008, prop=0x7fff000c, object=11166658) at composite.c:439
> #3  0x007e5298 in composition_compute_stop_pos (cmp_it=0x7fff0668, charpos=1, 
>     bytepos=1, endpos=501, string=11166658) at composite.c:1005
> #4  0x0045cbc8 in compute_stop_pos (it=0x7fff01a0) at xdisp.c:3492
> #5  0x0045c610 in handle_stop (it=0x7fff01a0) at xdisp.c:3390

(I'm going through old bug reports that have unfortunately gotten no
responses yet.)

This was reported five years ago and not handled at the time, so I
think it's unlikely that there'll be any progress here, and I'm closing
this bug report.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





      reply	other threads:[~2019-08-15  2:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-01  0:06 bug#16311: 24.3.50; Crash in next_interval Richard Stallman
2019-08-15  2:04 ` Lars Ingebrigtsen [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=87pnl76v69.fsf@mouse.gnus.org \
    --to=larsi@gnus.org \
    --cc=16311@debbugs.gnu.org \
    --cc=rms@gnu.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.