unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Jan D." <jan.h.d@swipnet.se>
Cc: 19660@debbugs.gnu.org, storm@cua.dk
Subject: bug#19660: Acknowledgement (24.4.51; Crash in draw_row_fringe_bitmaps)
Date: Mon, 26 Jan 2015 11:31:23 +0200	[thread overview]
Message-ID: <831tmhriqc.fsf@gnu.org> (raw)
In-Reply-To: <54C60503.5040308@swipnet.se>

> Date: Mon, 26 Jan 2015 10:12:35 +0100
> From: "Jan D." <jan.h.d@swipnet.se>
> CC: 19660@debbugs.gnu.org, "Kim F. Storm" <storm@cua.dk>
> 
> > If no other information emerges, my suggestion would be to remove the
> > assertion on master, and see if we get any bug reports.
> 
> No need for that, the NS version crashes later on if I remove that 
> assert.

Where does it crash, and why?  Another similar assertion or something
else?

> Better block input too much than to seldom I guess.

Right.  But understanding why this happens is better yet ;-)

Seriously: I thought we aren't supposed to be hit by this stuff, since
we now never run code out of an interrupt handler.  I guess I missed
something important.

> Unfortunately I managed to loose my .desktop that consistently triggered 
> the error, so I can't investigate further.

Don't you have a backup of that somewhere?





  reply	other threads:[~2015-01-26  9:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-23  6:30 bug#19660: 24.4.51; Crash in draw_row_fringe_bitmaps Jan D.
2015-01-23  7:05 ` Jan D.
     [not found] ` <handler.19660.B.1421994662864.ack@debbugs.gnu.org>
2015-01-25  9:17   ` bug#19660: Acknowledgement (24.4.51; Crash in draw_row_fringe_bitmaps) Jan D.
2015-01-25 15:46     ` Eli Zaretskii
2015-01-26  9:12       ` Jan D.
2015-01-26  9:31         ` Eli Zaretskii [this message]
2015-01-27  9:16           ` Jan D.
2015-01-27 17:41             ` Eli Zaretskii
2015-01-27 18:22               ` Jan D.
2015-01-27 19:13                 ` Eli Zaretskii
2015-01-26 11:10       ` Kim Storm

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=831tmhriqc.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=19660@debbugs.gnu.org \
    --cc=jan.h.d@swipnet.se \
    --cc=storm@cua.dk \
    /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).