unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Jim Rees via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: luangruo@yahoo.com, acm@muc.de, 65116@debbugs.gnu.org
Subject: bug#65116: 29.1; query-replace-read-args fails reading second arg in detached minibuf
Date: Sun, 14 Jan 2024 10:59:16 -0600	[thread overview]
Message-ID: <ZaQS5K3yoIiEECaE@rees.org> (raw)
In-Reply-To: <83le8sfnae.fsf@gnu.org>

While Po's patch fixes the read-args focus bug, I now have a new bug. It
happens irregularly and I can't say for sure yet that it's caused by Po's
patch. I don't know what triggers it but it seems I need to have at least
two edit frames open.

What happens first is the mouse pointer disappears, but I can still edit.
After a while emacs hangs and ignores all input. A bit later it won't even
redisplay frames on X exposure.

Here is the stack when it hangs:

% sudo gdb -batch -ex bt -p 174496
[New LWP 174497]
[New LWP 174498]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
0x00007f7f6ee3e9d8 in pthread_sigmask () from /usr/lib/libc.so.6
#0  0x00007f7f6ee3e9d8 in pthread_sigmask () at /usr/lib/libc.so.6
#1  0x000055e30363ed64 in block_interrupt_signal ()
#2  0x000055e3036d3a2a in really_call_select ()
#3  0x000055e3036d3ee9 in thread_select ()
#4  0x000055e3036ec3e4 in xg_select ()
#5  0x000055e3036baaa2 in wait_reading_process_output ()
#6  0x000055e303634352 in read_char ()
#7  0x000055e303635b0d in read_key_sequence ()
#8  0x000055e303636999 in command_loop_1 ()
#9  0x000055e3036870a9 in internal_condition_case ()
#10 0x000055e30362a3d2 in command_loop_2 ()
#11 0x000055e303687027 in internal_catch ()
#12 0x000055e30362a374 in command_loop ()
#13 0x000055e30362d1c3 in recursive_edit_1 ()
#14 0x000055e30362d418 in Frecursive_edit ()
#15 0x000055e30356b311 in main ()
[Inferior 1 (process 174496) detached]

Note this is Po's patch on top of stock 29.1. If I get ambitious I'll try
building from master.

I would not normally report a bug with such sketchy information but I
thought you should know. If I figure out anything more I will make a proper
bug report.





  parent reply	other threads:[~2024-01-14 16:59 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-06 17:18 bug#65116: 29.1; query-replace-read-args fails reading second arg in detached minibuf Jim Rees via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-07 15:57 ` Eli Zaretskii
2024-01-12  6:26   ` Jim Rees via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-12 12:00     ` Eli Zaretskii
2024-01-12 14:38       ` Jim Rees via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-12 15:25       ` Alan Mackenzie
2024-01-12 15:37 ` Alan Mackenzie
2024-01-12 15:59   ` Jim Rees via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-12 17:28     ` Alan Mackenzie
2024-01-12 18:57       ` Jim Rees via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-12 21:44         ` Alan Mackenzie
2024-01-13  6:34           ` Eli Zaretskii
2024-01-13  9:23             ` Alan Mackenzie
2024-01-13 13:47               ` Alan Mackenzie
2024-01-13 17:00                 ` Jim Rees via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-13 17:47                   ` Alan Mackenzie
2024-01-13 19:15                   ` Drew Adams
2024-01-13 20:18                     ` Alan Mackenzie
2024-01-13 21:19                       ` Drew Adams
2024-01-13 21:35                         ` Alan Mackenzie
2024-01-13 20:06                   ` Alan Mackenzie
2024-01-13 23:53                     ` Jim Rees via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-14  6:21                       ` Eli Zaretskii
2024-01-14 14:33                         ` Jim Rees via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-14 15:03                           ` Alan Mackenzie
2024-01-14 16:59                         ` Jim Rees via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-01-14 17:17                           ` Eli Zaretskii
2024-01-14 17:33                             ` Eli Zaretskii
2024-01-14 19:10                               ` Jim Rees via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-14 19:42                                 ` Eli Zaretskii
2024-01-15  0:27                                   ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-15  1:29                                     ` Jim Rees via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-15  3:38                                       ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-15  4:52                                         ` Jim Rees via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-15  6:31                                           ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-15 16:47                                             ` Jim Rees via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-14  0:27             ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-14 14:14               ` Alan Mackenzie

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=ZaQS5K3yoIiEECaE@rees.org \
    --to=bug-gnu-emacs@gnu.org \
    --cc=65116@debbugs.gnu.org \
    --cc=acm@muc.de \
    --cc=eliz@gnu.org \
    --cc=jim@rees.org \
    --cc=luangruo@yahoo.com \
    /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).