unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: <johann.hoechtl@inhouse.wko.at>
Cc: 64710@debbugs.gnu.org
Subject: bug#64710: 29.0.92; desktop session on terminal with speedbar crash
Date: Wed, 19 Jul 2023 15:40:12 +0300	[thread overview]
Message-ID: <835y6g5b2r.fsf@gnu.org> (raw)
In-Reply-To: <AS8PR01MB7559066BF74552DF9BE99D1DAC39A@AS8PR01MB7559.eurprd01.prod.exchangelabs.com> (johann.hoechtl@inhouse.wko.at)

> From: <johann.hoechtl@inhouse.wko.at>
> CC: <64710@debbugs.gnu.org>
> Date: Wed, 19 Jul 2023 06:38:22 +0000
> 
> The reason is actually not related to desktop-save. Unfortunately it is not easy to reproduce, as the behavior is not consistent. With the following recipe it shows quite regular though:
> 
> * Open a Windows Terminal, either Windows Terminal with bash or directly cmd.exe; Didn't test with powershell.
> * Run emacs -Q -nw
> * M-x speedbar-get-focus
> * Right-click with the mouse, so the speedbar menu displays <-- this step *seems* to trigger the bug more easily
> 
> Now the behavior is not consistent, either
> * Emacs enters a spin-lock and doesn't react; OR
> * Emacs crashes with a backtrace; OR
> * Emacs continues without any issues.

I cannot reproduce any problems with this recipe.  I tried many times,
and all I see is the drop-down menu drops and everything is OK.

Does this happen in any directory or just in some?  If some, can you
describe in more detail what is special about those directories and
what do you see after "M-x speedbar-get-focus"?

> I did however also notice in the past that Emacs on Windows (builds from https://alpha.gnu.org/gnu/emacs/pretest/windows/emacs-29/) had spurious crashes on other places, albeit only when running with -nw. So there might be a nasty (Windows - only) terminal display bug?

So maybe your build has a problem, or maybe the systems on which you
run Emacs somehow trigger a problem that doesn't happen elsewhere/

> I do attach the backtrace and hope that it might be useful.

Unfortunately, this kind of backtrace can only be interpreted on your
system.  If you have GNU Binutils installed, you can use the method
described in the node "Crashing" of the Emacs manual to produce file
names, function names, and line numbers from these addresses.





      reply	other threads:[~2023-07-19 12:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-18 12:14 bug#64710: 29.0.92; desktop session on terminal with speedbar crash johann.hoechtl
2023-07-18 16:24 ` Eli Zaretskii
2023-07-19  6:38   ` bug#64710: AW: " johann.hoechtl
2023-07-19 12:40     ` Eli Zaretskii [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

  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=835y6g5b2r.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=64710@debbugs.gnu.org \
    --cc=johann.hoechtl@inhouse.wko.at \
    /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).