From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Ami Fischman Newsgroups: gmane.emacs.bugs Subject: bug#12745: crash in bidi_pop_it during (idle) redisplay Date: Sat, 24 Nov 2012 20:52:19 -0800 Message-ID: References: <83624wt247.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=f46d043c821ae4feac04cf4a946b X-Trace: ger.gmane.org 1353819167 21673 80.91.229.3 (25 Nov 2012 04:52:47 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 25 Nov 2012 04:52:47 +0000 (UTC) Cc: Alp Aker , 12745@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Sun Nov 25 05:52:57 2012 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1TcUD1-0004y2-Io for geb-bug-gnu-emacs@m.gmane.org; Sun, 25 Nov 2012 05:52:47 +0100 Original-Received: from localhost ([::1]:51284 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TcUCq-0005l0-SA for geb-bug-gnu-emacs@m.gmane.org; Sat, 24 Nov 2012 23:52:36 -0500 Original-Received: from eggs.gnu.org ([208.118.235.92]:34745) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TcUCk-0005VL-E7 for bug-gnu-emacs@gnu.org; Sat, 24 Nov 2012 23:52:31 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TcUCj-0005Qn-Ac for bug-gnu-emacs@gnu.org; Sat, 24 Nov 2012 23:52:30 -0500 Original-Received: from debbugs.gnu.org ([140.186.70.43]:55270) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TcUCj-0005Qf-7Y for bug-gnu-emacs@gnu.org; Sat, 24 Nov 2012 23:52:29 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.72) (envelope-from ) id 1TcUEG-0002ps-5r for bug-gnu-emacs@gnu.org; Sat, 24 Nov 2012 23:54:04 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Ami Fischman Original-Sender: debbugs-submit-bounces@debbugs.gnu.org Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sun, 25 Nov 2012 04:54:04 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 12745 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 12745-submit@debbugs.gnu.org id=B12745.135381924310888 (code B ref 12745); Sun, 25 Nov 2012 04:54:04 +0000 Original-Received: (at 12745) by debbugs.gnu.org; 25 Nov 2012 04:54:03 +0000 Original-Received: from localhost ([127.0.0.1]:37282 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.72) (envelope-from ) id 1TcUEE-0002pO-8o for submit@debbugs.gnu.org; Sat, 24 Nov 2012 23:54:03 -0500 Original-Received: from mail-vb0-f44.google.com ([209.85.212.44]:64609) by debbugs.gnu.org with esmtp (Exim 4.72) (envelope-from ) id 1TcUE8-0002oi-Dc for 12745@debbugs.gnu.org; Sat, 24 Nov 2012 23:53:57 -0500 Original-Received: by mail-vb0-f44.google.com with SMTP id fc26so2915169vbb.3 for <12745@debbugs.gnu.org>; Sat, 24 Nov 2012 20:52:19 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=OM19bwJR8XVk2RdfqVv9hEzs5Lvj9AWT3hnA3VpCAbI=; b=a8+NH4DJ6Nn4DHTUpdApKchRBc5WTQ+SGj7DNRtMqKEF2FFuxspS4JDU6UwymmwG4H IBW67cdszL1YFHtzWbv9mOwyZFkAnm/PeEwNhvC5CI/xyOr3oX+UTcDjjgZOxfc/lYzH J1W4FQ75At9mmse68IeYGTilyHBYsrhMJQ5BqO/Vj/Ofd0Sx4tdZxc89FwgH3eruvCTl q7yHd2LqUGvK541Khj5CRgdj/7M0THJZt3+whTan7wnRFIdGyPevahb+pR3eKbE/PnfC 2jj49ydJ7sJdVsM1dDf7X5u9rT+1YUXuLuiqW5AjEvWR3A7gkk9nU9Q6mJPst2KGbBFM 9Tzg== Original-Received: by 10.220.152.204 with SMTP id h12mr12899308vcw.66.1353819139407; Sat, 24 Nov 2012 20:52:19 -0800 (PST) Original-Received: by 10.58.205.212 with HTTP; Sat, 24 Nov 2012 20:52:19 -0800 (PST) In-Reply-To: <83624wt247.fsf@gnu.org> X-Gm-Message-State: ALoCoQl7/6T+rX9OE0cPZUl9Ej4Tj9nXikTESVWyhiT6x8xulxQUkP1swA+em04s5pAhX4DwyuE/ X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.13 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x X-Received-From: 140.186.70.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:67430 Archived-At: --f46d043c821ae4feac04cf4a946b Content-Type: text/plain; charset=ISO-8859-1 > > If you don't have 110767, then why is it interesting to report this crash? That revision was supposed to fix precisely this crash. > I didn't get the impression from our previous exchange that you had such a high confidence in the connection (just that you were sure it was fixing a bug, not that it was necessarily the bug I was tripping over). > The current revision numbers on the emacs-24 branch and on the trunk > are 110941 and 110993, respectively. So why would you use such an old > version, from more than 3 weeks ago? > This bug took hours/days to manifest; I wanted to see whether trunk already had it fixed. It seems that it was at least partially fixed since this time it took a lot longer to manifest. I'll sync & rebuild and will report back if I get another one of these. --f46d043c821ae4feac04cf4a946b Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
If you don't have 110767, then why is it interesting t= o report this
crash? =A0That revision was supposed to fix precisely this crash.

I didn't get the impression from our previou= s exchange that you had such a high confidence in the connection (just that= you were sure it was fixing a bug, not that it was necessarily the bug I w= as tripping over).
=A0
The current revision numbers o= n the emacs-24 branch and on the trunk
are 110941 and 110993, respectively. =A0So why would you use such an old version, from more than 3 weeks ago?

Th= is bug took hours/days to manifest; I wanted to see whether trunk already h= ad it fixed. =A0It seems that it was at least partially fixed since this ti= me it took a lot longer to manifest.

I'll sync & rebuild and will report back if I g= et another one of these.=A0
--f46d043c821ae4feac04cf4a946b--