From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Ken Raeburn Newsgroups: gmane.emacs.bugs Subject: bug#23013: 25.0.92; assertion failure on marker outside text range in echo area Date: Thu, 7 Apr 2016 18:32:51 -0400 Message-ID: References: <6e8u1kyguc.fsf@just-testing.permabit.com> <6e7fh3bm7h.fsf@just-testing.permabit.com> <837fh3bljl.fsf@gnu.org> <8337rrbiuh.fsf@gnu.org> <83zitya15t.fsf@gnu.org> <838u1h9gq1.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=001a11401ab2a89c20052feca877 X-Trace: ger.gmane.org 1460068399 24609 80.91.229.3 (7 Apr 2016 22:33:19 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 7 Apr 2016 22:33:19 +0000 (UTC) Cc: 23013@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Fri Apr 08 00:33:10 2016 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 1aoIUA-0000pQ-2B for geb-bug-gnu-emacs@m.gmane.org; Fri, 08 Apr 2016 00:33:10 +0200 Original-Received: from localhost ([::1]:52551 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aoIU8-0007SX-S6 for geb-bug-gnu-emacs@m.gmane.org; Thu, 07 Apr 2016 18:33:08 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:42728) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aoIU5-0007QG-7L for bug-gnu-emacs@gnu.org; Thu, 07 Apr 2016 18:33:06 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aoIU1-0007B8-Vk for bug-gnu-emacs@gnu.org; Thu, 07 Apr 2016 18:33:05 -0400 Original-Received: from debbugs.gnu.org ([208.118.235.43]:40973) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aoIU1-0007B2-T8 for bug-gnu-emacs@gnu.org; Thu, 07 Apr 2016 18:33:01 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1aoIU1-0003X2-Or for bug-gnu-emacs@gnu.org; Thu, 07 Apr 2016 18:33:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Ken Raeburn Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 07 Apr 2016 22:33:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 23013 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 23013-submit@debbugs.gnu.org id=B23013.146006838013569 (code B ref 23013); Thu, 07 Apr 2016 22:33:01 +0000 Original-Received: (at 23013) by debbugs.gnu.org; 7 Apr 2016 22:33:00 +0000 Original-Received: from localhost ([127.0.0.1]:53310 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1aoIU0-0003Wm-3Y for submit@debbugs.gnu.org; Thu, 07 Apr 2016 18:33:00 -0400 Original-Received: from mail-lf0-f48.google.com ([209.85.215.48]:35375) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1aoITx-0003WX-Qq for 23013@debbugs.gnu.org; Thu, 07 Apr 2016 18:32:58 -0400 Original-Received: by mail-lf0-f48.google.com with SMTP id c126so67231202lfb.2 for <23013@debbugs.gnu.org>; Thu, 07 Apr 2016 15:32:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=permabit.com; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=bTRf4LZJptezD4OLepwXzCYZawxJCg/Hzl+0NgPZsPw=; b=IFcNC4Xp1WDStPMqecXk6FG1ZI8USe9hEEcSH3OfIBF4Hw8G/Ml0lYUaZzTXCfv+3W toTY/7w7N1RcLVDxvlPv8LMrhEtDMOtbuSgeuyarTTQBSeIR/epUPZ3TqcbKzqu9va8h asOUp3xdmSLzgF3Www/ufp5pv5/5xbHldvNNQ= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=bTRf4LZJptezD4OLepwXzCYZawxJCg/Hzl+0NgPZsPw=; b=Tt9G4P/oHCNXdvyhdum7AVMifyIDxKBzm2QNNhV99i/VNsYSDe1hqqOpiQnV+Qflig ZRY5KFr2nb1kRGPb8K9e02VVx+HQ7Rj9uqRgfz+2Kic140xFe/8Y/m/xZSa7grzh0cEj /WwSVEGlAtQ114qK/0ePff6njG33QiKedurZ0te6BHLxO6rmFZFvPgQxCc4uKPN5F9ef hXKzTmC4FBWF+FbVU+G6piSUfP0WrcFC/QAln4E+TyBgpNBQ7LgfzB9DfPWXFXg5OY8I PrC1ztdd0OfPsVNO1GOLT8uii+ENp8561wE0Wu5x8YABcZ8eMx0s4V+lbpyU9sfEV4do aJAA== X-Gm-Message-State: AD7BkJKMmcwe521yxO6j6vZZ0DLoEWBpBzq++h7uqvmfXtjoJNK7Cqrxnr0XoXA0YXsVZUJMX9/gV/UJHSs6Hqyv X-Received: by 10.25.146.206 with SMTP id u197mr2293980lfd.139.1460068371950; Thu, 07 Apr 2016 15:32:51 -0700 (PDT) Original-Received: by 10.112.84.197 with HTTP; Thu, 7 Apr 2016 15:32:51 -0700 (PDT) In-Reply-To: <838u1h9gq1.fsf@gnu.org> X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 208.118.235.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" Xref: news.gmane.org gmane.emacs.bugs:116177 Archived-At: --001a11401ab2a89c20052feca877 Content-Type: text/plain; charset=UTF-8 On Thu, Mar 17, 2016 at 1:06 PM, Eli Zaretskii wrote: > I've reviewed the changes between 25.0.90 and 25.0.92. I see nothing > that could be directly linked to this problem. The only commits that > might be even remotely related are these 3: > > d82f24ba8530eb8de04a319cc80742a0a953040e > This could be interesting... > 84829495b5746417f5eaf9be693fb35f0509697a > scroll-conservatively is 0, at least in the core file, and it looks like the only mode I use that changes it is jabber-chat-mode which sets it to 5, so either way it shouldn't reach the path where this change occurred. > 06a872b71d6580e0699600844bb9526602437990 > Probably not relevant as I was only using X frames. There's the initial frame created in daemon mode, which has FRAME_VISIBLE_P true but FRAME_GARBAGED_P false (also FRAME_TERMCAP_P and FRAME_MSDOS_P false) so it wouldn't follow that path. > > Maybe you should try reverting these one by one. > I have no reliable way of reproducing the problem, so not hitting another crash once a change is reverted wouldn't tell me much. Is there something further I could introduce a check for to see if one of these patches might be causing the problem? > > It could also happen that the assertions you saw in 25.0.90 are caused > by the same problem that now causes this bug. Any idea if those > assertions were for the mini-window as well? > Both assertions in .90 were in find_last_row_displaying_text, checking row->enabled_p. The window being examined (next frame up, try_window_id) is the root window of its frame. Redisplay is being done during a call to wait_reading_process_output. So it doesn't look very similar. --001a11401ab2a89c20052feca877 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On T= hu, Mar 17, 2016 at 1:06 PM, Eli Zaretskii <eliz@gnu.org> wrote:<= br>
I've reviewed the changes between 25.= 0.90 and 25.0.92.=C2=A0 I see nothing
that could be directly linked to this problem.=C2=A0 The only commits that<= br> might be even remotely related are these 3:

=C2=A0 d82f24ba8530eb8de04a319cc80742a0a953040e

This could be interesting...
=C2=A0
=C2=A0 84829495b5746417f5eaf9be693fb35f0509697a

scroll-conservatively is 0, at least in the core file, and it look= s like the only mode I use that changes it is jabber-chat-mode which sets i= t to 5, so either way it shouldn't reach the path where this change occ= urred.
=C2=A0
=C2=A0 06a872b71d6580e0699600844bb9526602437990

Probably not relevant as I was only using X frames. There's th= e initial frame created in daemon mode, which has FRAME_VISIBLE_P true but = FRAME_GARBAGED_P false (also FRAME_TERMCAP_P and FRAME_MSDOS_P false) so it= wouldn't follow that path.
=C2=A0

Maybe you should try reverting these one by one.

<= /div>
I have no reliable way of reproducing the problem, so not hitting= another crash once a change is reverted wouldn't tell me much. Is ther= e something further I could introduce a check for to see if one of these pa= tches might be causing the problem?
=C2=A0

It could also happen that the assertions you saw in 25.0.90 are caused
by the same problem that now causes this bug.=C2=A0 Any idea if those
assertions were for the mini-window as well?

Both assertions in = .90 were in find_last_row_displaying_text, checking row->enabled_p. The = window being examined (next frame up, try_window_id) is the root window of = its frame. Redisplay is being done during a call to wait_reading_process_ou= tput. So it doesn't look very similar.
--001a11401ab2a89c20052feca877--