unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Joseph Mingrone <jrm@ftfl.ca>
Cc: 22214@debbugs.gnu.org, bburns.km@gmail.com
Subject: bug#22214: 25.0.50; lock up with gui dialogs and clipmon-mode
Date: Mon, 21 Dec 2015 19:50:59 +0200	[thread overview]
Message-ID: <8337uvsnb0.fsf@gnu.org> (raw)
In-Reply-To: <86k2o7g3ec.fsf@phe.ftfl.ca> (message from Joseph Mingrone on Mon, 21 Dec 2015 12:41:47 -0400)

> From: Joseph Mingrone <jrm@ftfl.ca>
> Cc: 22214@debbugs.gnu.org,  bburns.km@gmail.com
> Date: Mon, 21 Dec 2015 12:41:47 -0400
> 
> Thread 3 (Thread 1902400 (LWP 100743)):
> #0  0x0000000807444cfa in _sigprocmask () from /lib/libc.so.7
> #1  0x0000000804656526 in pthread_sigmask () from /lib/libthr.so.3
> #2  0x00000000007ab8e9 in block_atimers (oldset=0x7fffffff7970) at atimer.c:70
> #3  0x00000000007abffc in do_pending_atimers () at atimer.c:434
> #4  0x00000000005f803e in process_pending_signals () at keyboard.c:7043
> #5  0x00000000006c1559 in Fmake_list (length=0, init=0) at alloc.c:2718
> #6  0x0000000000713c2a in concat (nargs=1, args=0x7fffffff7b28, target_type=Lisp_Cons, last_special=false) at fns.c:633
> #7  0x00000000007135d2 in Fcopy_sequence (arg=18186131) at fns.c:501
> #8  0x00000000005f25b3 in timer_check () at keyboard.c:4452

Thanks.

Can you find out which thread uses up the CPU?  If that's this thread
(the Emacs application main thread), can you use the technique
described in etc/DEBUG under "If the symptom of the bug is that Emacs
fails to respond" to find out whether Emacs is looping and where?





  reply	other threads:[~2015-12-21 17:50 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-20  6:26 bug#22214: 25.0.50; lock up with gui dialogs and clipmon-mode Joseph Mingrone
2015-12-20 15:54 ` Eli Zaretskii
2015-12-21  2:31   ` Joseph Mingrone
2015-12-21 15:24     ` Eli Zaretskii
2015-12-21 16:41       ` Joseph Mingrone
2015-12-21 17:50         ` Eli Zaretskii [this message]
2015-12-21 19:42           ` Joseph Mingrone
2015-12-21  0:21 ` Brian Burns
2015-12-21  0:45   ` Joseph Mingrone
2015-12-22  7:56     ` Brian Burns
2015-12-21 15:26   ` Eli Zaretskii
2015-12-22  5:21 ` Joseph Mingrone
2015-12-22 16:06   ` Eli Zaretskii
2015-12-23 17:00     ` Joseph Mingrone
2015-12-23 17:12       ` Eli Zaretskii
2015-12-23 18:18         ` Joseph Mingrone
2015-12-23 18:22           ` Eli Zaretskii
2015-12-23 20:16             ` Brian Burns
2015-12-23 21:21               ` Joseph Mingrone
2015-12-24  7:43                 ` Brian Burns
2015-12-24 16:20                   ` Eli Zaretskii
2015-12-27  7:29                     ` Brian Burns
2022-04-23 14:06                 ` Lars Ingebrigtsen
2022-04-24 13:23                   ` Joseph Mingrone
2022-04-25  0:50                     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-23  8:02                       ` Lars Ingebrigtsen
2022-05-23 19:02                         ` Joseph Mingrone
2022-05-24  0:27                           ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-29 15:51                             ` Joseph Mingrone
2022-05-29 23:58                               ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-30  6:05                               ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-30 13:00                                 ` Joseph Mingrone
2022-05-30 13:34                                   ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=8337uvsnb0.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=22214@debbugs.gnu.org \
    --cc=bburns.km@gmail.com \
    --cc=jrm@ftfl.ca \
    /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).