GNU logs - #31671, boring messages

Message sent to bug-gnu-emacs@HIDDEN:

Subject: bug#31671: 26.1; edebug-defun doesn't step if functions run in a separate thread
Resent-From: Raimon Grau <raimon@HIDDEN>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
Resent-CC: bug-gnu-emacs@HIDDEN
Resent-Date: Thu, 31 May 2018 17:45:01 +0000
Resent-Message-ID: <handler.31671.B.1527788642550 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
To: 31671 <at> debbugs.gnu.org
From: Raimon Grau <raimon@HIDDEN>
Date: Thu, 31 May 2018 18:37:17 +0100
Message-ID: <87muwfsp4i.fsf@HIDDEN>
MIME-Version: 1.0
Content-Type: text/plain
Precedence: list
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>

Using edebug-defun to instrument a function and running that function in
a separate thread using `make-thread' makes triggers the breakpoint but
leaves the bufer in read-only-mode but the user can't interact with
edebug in any way.

Steps to reproduce (ubuntu 16.04):
- start emacs with emacs -Q  . 
- in the *scratch* buffer, write:
(defun foo ()
  (message "hi"))

(make-thread 'foo)
- edebug-defun function foo
- c-x c-e the (make-thread 'foo) sexp
- *scratch* buffer point moves to the beginning of function foo
- press `n` and the minibuffers says: "No catch for tag: exit, nil". The
  whole buffer is in read-only mode. modeline has
  "(Lisp Interaction *Debugging* ElDoc)"

The "Recent messages" below correspond exactly to that sequence of
commands.


In GNU Emacs 26.1 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.18.9)
 of 2018-05-10 built on raikong
Repository revision: 1d9e66aea17787e03954f32c6cd7561c881bb444
Windowing system distributor 'The X.Org Foundation', version 11.0.11905000
System Description:	Ubuntu 16.04.4 LTS

Recent messages:
foo
Edebug: foo
foo
#<thread 0x1399d20>

edebug-set-mode: No catch for tag: exit, nil
Making completion list...
(#<thread 0xc11460> #<thread 0x1399d20>)
Making completion list... [2 times]
Edebug will stop after next eval.
edebug-bounce-point: Edebug is not active
command-execute: Buffer is read-only: #<buffer *scratch*>

Configured using:
 'configure --prefix=/home/rgrau/emacs-git
 PKG_CONFIG_PATH=/home/rgrau/.guix-profile/lib/pkgconfig'

Configured features:
XPM JPEG TIFF GIF PNG RSVG IMAGEMAGICK SOUND GPM DBUS GSETTINGS NOTIFY
ACL LIBSELINUX GNUTLS LIBXML2 FREETYPE M17N_FLT LIBOTF XFT ZLIB
TOOLKIT_SCROLL_BARS GTK3 X11 THREADS LCMS2

Important settings:
  value of $LC_MONETARY: es_ES.UTF-8
  value of $LC_NUMERIC: es_ES.UTF-8
  value of $LC_TIME: es_ES.UTF-8
  value of $LANG: en_US.UTF-8
  locale-coding-system: utf-8-unix

Major mode: Lisp Interaction

Minor modes in effect:
  edebug-mode: t
  tooltip-mode: t
  global-eldoc-mode: t
  eldoc-mode: t
  electric-indent-mode: t
  mouse-wheel-mode: t
  tool-bar-mode: t
  menu-bar-mode: t
  file-name-shadow-mode: t
  global-font-lock-mode: t
  font-lock-mode: t
  blink-cursor-mode: t
  auto-composition-mode: t
  auto-encryption-mode: t
  auto-compression-mode: t
  buffer-read-only: t
  line-number-mode: t
  transient-mark-mode: t

Load-path shadows:
None found.

Features:
(shadow sort mail-extr emacsbug message rmc puny seq byte-opt gv
bytecomp byte-compile cconv dired dired-loaddefs format-spec rfc822 mml
mml-sec password-cache epa derived epg epg-config gnus-util rmail
rmail-loaddefs mm-decode mm-bodies mm-encode mail-parse rfc2231
mailabbrev gmm-utils mailheader sendmail rfc2047 rfc2045 ietf-drums
mm-util mail-prsvr mail-utils edebug easymenu cl-loaddefs cl-lib
elec-pair time-date mule-util tooltip eldoc electric uniquify ediff-hook
vc-hooks lisp-float-type mwheel term/x-win x-win term/common-win x-dnd
tool-bar dnd fontset image regexp-opt fringe tabulated-list replace
newcomment text-mode elisp-mode lisp-mode prog-mode register page
menu-bar rfn-eshadow isearch timer select scroll-bar mouse jit-lock
font-lock syntax facemenu font-core term/tty-colors frame cl-generic
cham georgian utf-8-lang misc-lang vietnamese tibetan thai tai-viet lao
korean japanese eucjp-ms cp51932 hebrew greek romanian slovak czech
european ethiopic indian cyrillic chinese composite charscript charprop
case-table epa-hook jka-cmpr-hook help simple abbrev obarray minibuffer
cl-preloaded nadvice loaddefs button faces cus-face macroexp files
text-properties overlay sha1 md5 base64 format env code-pages mule
custom widget hashtable-print-readable backquote dbusbind inotify lcms2
dynamic-setting system-font-setting font-render-setting move-toolbar gtk
x-toolkit x multi-tty make-network-process emacs)

Memory information:
((conses 16 97842 12105)
 (symbols 48 20713 1)
 (miscs 40 59 143)
 (strings 32 29196 1060)
 (string-bytes 1 768686)
 (vectors 16 14550)
 (vector-slots 8 496991 7738)
 (floats 8 53 323)
 (intervals 56 254 7)
 (buffers 992 12)
 (heap 1024 32030 1223))

Message sent:

Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailer: MIME-tools 5.505 (Entity 5.505)
Content-Type: text/plain; charset=utf-8
X-Loop: help-debbugs@HIDDEN
From: help-debbugs@HIDDEN (GNU bug Tracking System)
To: Raimon Grau <raimon@HIDDEN>
Subject: bug#31671: Acknowledgement (26.1; edebug-defun doesn't step if
 functions run in a separate thread)
Message-ID: <handler.31671.B.1527788642550.ack <at> debbugs.gnu.org>
References: <87muwfsp4i.fsf@HIDDEN>
X-Gnu-PR-Message: ack 31671
X-Gnu-PR-Package: emacs
Reply-To: 31671 <at> debbugs.gnu.org
Date: Thu, 31 May 2018 17:45:02 +0000

Thank you for filing a new bug report with debbugs.gnu.org.

This is an automatically generated reply to let you know your message
has been received.

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

Your message has been sent to the package maintainer(s):
 bug-gnu-emacs@HIDDEN

If you wish to submit further information on this problem, please
send it to 31671 <at> debbugs.gnu.org.

Please do not send mail to help-debbugs@HIDDEN unless you wish
to report a problem with the Bug-tracking system.

--=20
31671: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=3D31671
GNU Bug Tracking System
Contact help-debbugs@HIDDEN with problems

Message sent to bug-gnu-emacs@HIDDEN:

Subject: bug#31671: 26.1; edebug-defun doesn't step if functions run in a separate thread
Resent-From: Eli Zaretskii <eliz@HIDDEN>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
Resent-CC: bug-gnu-emacs@HIDDEN
Resent-Date: Mon, 04 Jun 2018 16:57:02 +0000
Resent-Message-ID: <handler.31671.B31671.15281313914172 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
To: Raimon Grau <raimon@HIDDEN>
Cc: 31671 <at> debbugs.gnu.org
Reply-To: Eli Zaretskii <eliz@HIDDEN>
Date: Mon, 04 Jun 2018 19:56:28 +0300
Message-Id: <83r2lmbidf.fsf@HIDDEN>
From: Eli Zaretskii <eliz@HIDDEN>
In-reply-to: <87muwfsp4i.fsf@HIDDEN> (message from Raimon Grau on Thu, 31
 May 2018 18:37:17 +0100)
References: <87muwfsp4i.fsf@HIDDEN>
Precedence: list
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>

> From: Raimon Grau <raimon@HIDDEN>
> Date: Thu, 31 May 2018 18:37:17 +0100
> 
> Using edebug-defun to instrument a function and running that function in
> a separate thread using `make-thread' makes triggers the breakpoint but
> leaves the bufer in read-only-mode but the user can't interact with
> edebug in any way.
> 
> Steps to reproduce (ubuntu 16.04):
> - start emacs with emacs -Q  . 
> - in the *scratch* buffer, write:
> (defun foo ()
>   (message "hi"))
> 
> (make-thread 'foo)
> - edebug-defun function foo
> - c-x c-e the (make-thread 'foo) sexp
> - *scratch* buffer point moves to the beginning of function foo
> - press `n` and the minibuffers says: "No catch for tag: exit, nil". The
>   whole buffer is in read-only mode. modeline has
>   "(Lisp Interaction *Debugging* ElDoc)"

The problem here is that Edebug enters recursive-editing (on the
non-main thread which runs the function 'foo'), then waits for the
user to press a key.  While it waits, it releases the global lock, and
the main thread starts running.  So when you press a key, you are on a
different thread, and 'throw' doesn't have a matching 'catch' (because
that 'catch' is stored with the handlers of the thread which runs
'foo'.

Not yet sure how to deal with this.  Thoughts and ideas are welcome.

Message sent to bug-gnu-emacs@HIDDEN:

Subject: bug#31671: 26.1; edebug-defun doesn't step if functions run in a separate thread
Resent-From: Drew Adams <drew.adams@HIDDEN>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
Resent-CC: bug-gnu-emacs@HIDDEN
Resent-Date: Mon, 04 Jun 2018 17:25:01 +0000
Resent-Message-ID: <handler.31671.B31671.152813305014411 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
To: Eli Zaretskii <eliz@HIDDEN>, Raimon Grau <raimon@HIDDEN>
Cc: 31671 <at> debbugs.gnu.org
MIME-Version: 1.0
Message-ID: <b6ac5457-5353-4a73-9835-2c131d08398f@default>
Date: Mon, 4 Jun 2018 10:23:58 -0700 (PDT)
From: Drew Adams <drew.adams@HIDDEN>
References: <<87muwfsp4i.fsf@HIDDEN>> <<83r2lmbidf.fsf@HIDDEN>>
In-Reply-To: <<83r2lmbidf.fsf@HIDDEN>>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Precedence: list
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>

> The problem here is that Edebug enters recursive-editing (on the
> non-main thread which runs the function 'foo'), then waits for the
> user to press a key.  While it waits, it releases the global lock, and
> the main thread starts running.  So when you press a key, you are on a
> different thread, and 'throw' doesn't have a matching 'catch' (because
> that 'catch' is stored with the handlers of the thread which runs
> 'foo'.
>=20
> Not yet sure how to deal with this.  Thoughts and ideas are welcome.

Not really following this thread, and 100% unknowledgable
about Emacs threading.  But somewhat curious: Does the same
problem exist for plain `debug' as for `edebug'?

Message sent to bug-gnu-emacs@HIDDEN:

X-Loop: help-debbugs@HIDDEN
Subject: bug#31671: 26.1; edebug-defun doesn't step if functions run in a separate thread
Resent-From: Eli Zaretskii <eliz@HIDDEN>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
Resent-CC: bug-gnu-emacs@HIDDEN
Resent-Date: Tue, 05 Jun 2018 14:48:02 +0000
Resent-Message-ID: <handler.31671.B31671.15282100736656 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
X-GNU-PR-Message: followup 31671
X-GNU-PR-Package: emacs
X-GNU-PR-Keywords: 
To: Drew Adams <drew.adams@HIDDEN>
Cc: raimon@HIDDEN, 31671 <at> debbugs.gnu.org
Reply-To: Eli Zaretskii <eliz@HIDDEN>
Received: via spool by 31671-submit <at> debbugs.gnu.org id=B31671.15282100736656
          (code B ref 31671); Tue, 05 Jun 2018 14:48:02 +0000
Received: (at 31671) by debbugs.gnu.org; 5 Jun 2018 14:47:53 +0000
Received: from localhost ([127.0.0.1]:35278 helo=debbugs.gnu.org)
	by debbugs.gnu.org with esmtp (Exim 4.84_2)
	(envelope-from <debbugs-submit-bounces <at> debbugs.gnu.org>)
	id 1fQDFY-0001jI-RK
	for submit <at> debbugs.gnu.org; Tue, 05 Jun 2018 10:47:53 -0400
Received: from eggs.gnu.org ([208.118.235.92]:57375)
 by debbugs.gnu.org with esmtp (Exim 4.84_2)
 (envelope-from <eliz@HIDDEN>) id 1fQDFW-0001j0-CJ
 for 31671 <at> debbugs.gnu.org; Tue, 05 Jun 2018 10:47:50 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
 (envelope-from <eliz@HIDDEN>) id 1fQDFN-0000eU-TJ
 for 31671 <at> debbugs.gnu.org; Tue, 05 Jun 2018 10:47:45 -0400
X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on eggs.gnu.org
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=disabled
 version=3.3.2
Received: from fencepost.gnu.org ([2001:4830:134:3::e]:45024)
 by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from <eliz@HIDDEN>)
 id 1fQDFN-0000eP-OR; Tue, 05 Jun 2018 10:47:41 -0400
Received: from [176.228.60.248] (port=3864 helo=home-c4e4a596f7)
 by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256)
 (Exim 4.82) (envelope-from <eliz@HIDDEN>)
 id 1fQDFN-0002ic-5t; Tue, 05 Jun 2018 10:47:41 -0400
Date: Tue, 05 Jun 2018 17:47:52 +0300
Message-Id: <83602xb887.fsf@HIDDEN>
From: Eli Zaretskii <eliz@HIDDEN>
In-reply-to: <b6ac5457-5353-4a73-9835-2c131d08398f@default> (message from Drew
 Adams on Mon, 4 Jun 2018 10:23:58 -0700 (PDT))
References: <<87muwfsp4i.fsf@HIDDEN>> <<83r2lmbidf.fsf@HIDDEN>>
 <b6ac5457-5353-4a73-9835-2c131d08398f@default>
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic]
X-Received-From: 2001:4830:134:3::e
X-Spam-Score: -5.0 (-----)
X-BeenThere: debbugs-submit <at> debbugs.gnu.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: <debbugs-submit.debbugs.gnu.org>
List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe>
List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/>
List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org>
List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help>
List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe>
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
X-Spam-Score: -6.0 (------)

> Date: Mon, 4 Jun 2018 10:23:58 -0700 (PDT)
> From: Drew Adams <drew.adams@HIDDEN>
> Cc: 31671 <at> debbugs.gnu.org
> 
> > The problem here is that Edebug enters recursive-editing (on the
> > non-main thread which runs the function 'foo'), then waits for the
> > user to press a key.  While it waits, it releases the global lock, and
> > the main thread starts running.  So when you press a key, you are on a
> > different thread, and 'throw' doesn't have a matching 'catch' (because
> > that 'catch' is stored with the handlers of the thread which runs
> > 'foo'.
> > 
> > Not yet sure how to deal with this.  Thoughts and ideas are welcome.
> 
> Not really following this thread, and 100% unknowledgable
> about Emacs threading.  But somewhat curious: Does the same
> problem exist for plain `debug' as for `edebug'?

Yes.  Modify the recipe like this, and you have the same problem with
'debug':

  emacs -Q
  Type:

    (defun foo ()
      (message "Hi"))

  Eval the function to define it.
  M-x debug-on-entry RET foo RET
  M-: (make-thread 'foo) RET

  Type 'd' in the backtrace that Emacs presents.

Message sent to bug-gnu-emacs@HIDDEN:

X-Loop: help-debbugs@HIDDEN
Subject: bug#31671: 26.1; edebug-defun doesn't step if functions run in a separate thread
Resent-From: Eli Zaretskii <eliz@HIDDEN>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
Resent-CC: bug-gnu-emacs@HIDDEN
Resent-Date: Tue, 05 Jun 2018 14:52:01 +0000
Resent-Message-ID: <handler.31671.B31671.15282102647020 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
X-GNU-PR-Message: followup 31671
X-GNU-PR-Package: emacs
X-GNU-PR-Keywords: 
To: raimon@HIDDEN
Cc: 31671 <at> debbugs.gnu.org
Reply-To: Eli Zaretskii <eliz@HIDDEN>
Received: via spool by 31671-submit <at> debbugs.gnu.org id=B31671.15282102647020
          (code B ref 31671); Tue, 05 Jun 2018 14:52:01 +0000
Received: (at 31671) by debbugs.gnu.org; 5 Jun 2018 14:51:04 +0000
Received: from localhost ([127.0.0.1]:35289 helo=debbugs.gnu.org)
	by debbugs.gnu.org with esmtp (Exim 4.84_2)
	(envelope-from <debbugs-submit-bounces <at> debbugs.gnu.org>)
	id 1fQDId-0001p9-Kj
	for submit <at> debbugs.gnu.org; Tue, 05 Jun 2018 10:51:03 -0400
Received: from eggs.gnu.org ([208.118.235.92]:58365)
 by debbugs.gnu.org with esmtp (Exim 4.84_2)
 (envelope-from <eliz@HIDDEN>) id 1fQDIc-0001oe-3p
 for 31671 <at> debbugs.gnu.org; Tue, 05 Jun 2018 10:51:02 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
 (envelope-from <eliz@HIDDEN>) id 1fQDIT-0002Al-Q7
 for 31671 <at> debbugs.gnu.org; Tue, 05 Jun 2018 10:50:57 -0400
X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on eggs.gnu.org
X-Spam-Level: 
X-Spam-Status: No, score=-0.5 required=5.0 tests=BAYES_05 autolearn=disabled
 version=3.3.2
Received: from fencepost.gnu.org ([2001:4830:134:3::e]:45070)
 by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from <eliz@HIDDEN>)
 id 1fQDIT-0002Ah-LY; Tue, 05 Jun 2018 10:50:53 -0400
Received: from [176.228.60.248] (port=3872 helo=home-c4e4a596f7)
 by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256)
 (Exim 4.82) (envelope-from <eliz@HIDDEN>)
 id 1fQDIT-000306-1p; Tue, 05 Jun 2018 10:50:53 -0400
Date: Tue, 05 Jun 2018 17:51:03 +0300
Message-Id: <834lihb82w.fsf@HIDDEN>
From: Eli Zaretskii <eliz@HIDDEN>
In-reply-to: <83r2lmbidf.fsf@HIDDEN> (message from Eli Zaretskii on Mon, 04
 Jun 2018 19:56:28 +0300)
References: <87muwfsp4i.fsf@HIDDEN> <83r2lmbidf.fsf@HIDDEN>
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic]
X-Received-From: 2001:4830:134:3::e
X-Spam-Score: -5.0 (-----)
X-BeenThere: debbugs-submit <at> debbugs.gnu.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: <debbugs-submit.debbugs.gnu.org>
List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe>
List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/>
List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org>
List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help>
List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe>
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
X-Spam-Score: -6.0 (------)

> Date: Mon, 04 Jun 2018 19:56:28 +0300
> From: Eli Zaretskii <eliz@HIDDEN>
> Cc: 31671 <at> debbugs.gnu.org
> 
> The problem here is that Edebug enters recursive-editing (on the
> non-main thread which runs the function 'foo'), then waits for the
> user to press a key.  While it waits, it releases the global lock, and
> the main thread starts running.  So when you press a key, you are on a
> different thread, and 'throw' doesn't have a matching 'catch' (because
> that 'catch' is stored with the handlers of the thread which runs
> 'foo'.
> 
> Not yet sure how to deal with this.  Thoughts and ideas are welcome.

Any objections to the following band-aid?  (Of course, user-error does
nothing visible on non-main threads, and you have too invoke
thread-last-error to see the error message, but at least we don't
leave around a thread in limbo waiting forever for input that will
never come...)

--- src/thread.c~0	2018-01-28 06:56:25.000000000 +0200
+++ src/thread.c	2018-06-05 17:25:43.147566500 +0300
@@ -980,6 +980,23 @@ DEFUN ("thread-last-error", Fthread_last
   return last_thread_error;
 }
 
+DEFUN ("main-thread-p", Fmain_thread_p, Smain_thread_p, 0, 1, 0,
+       doc: /* Return non-nil if THREAD is the main thread.
+If THREAD is nil or omitted, it defaults to the current thread.  */)
+  (Lisp_Object thread)
+{
+  struct thread_state *tstate;
+
+  if (NILP (thread))
+    tstate = current_thread;
+  else
+    {
+      CHECK_THREAD (thread);
+      tstate = XTHREAD (thread);
+    }
+  return main_thread_p (tstate) ? Qt : Qnil;
+}
+
 
 
 bool
@@ -1073,6 +1090,7 @@ syms_of_threads (void)
       defsubr (&Scondition_mutex);
       defsubr (&Scondition_name);
       defsubr (&Sthread_last_error);
+      defsubr (&Smain_thread_p);
 
       staticpro (&last_thread_error);
       last_thread_error = Qnil;
--- lisp/emacs-lisp/edebug.el~0	2018-03-14 06:39:59.000000000 +0200
+++ lisp/emacs-lisp/edebug.el	2018-06-05 17:19:52.017355000 +0300
@@ -2425,6 +2425,8 @@
   (if inhibit-redisplay
       ;; Don't really try to enter edebug within an eval from redisplay.
       value
+    (or (main-thread-p)
+        (user-error "Debugging on non-main thread is not yet supported"))
     ;; Check breakpoints and pending input.
     ;; If edebug display should be updated, call edebug--display.
     ;; Return value.
--- lisp/emacs-lisp/debug.el~0	2018-01-03 13:08:56.000000000 +0200
+++ lisp/emacs-lisp/debug.el	2018-06-05 17:31:39.765134800 +0300
@@ -147,6 +147,8 @@
   (if inhibit-redisplay
       ;; Don't really try to enter debugger within an eval from redisplay.
       debugger-value
+    (or (main-thread-p)
+        (user-error "Debugging on non-main thread is not yet supported"))
     (unless noninteractive
       (message "Entering debugger..."))
     (let (debugger-value
--- doc/lispref/threads.texi~0	2018-01-03 13:08:46.000000000 +0200
+++ doc/lispref/threads.texi	2018-06-05 17:29:47.030735200 +0300
@@ -122,6 +122,12 @@
 Return the current thread.
 @end defun
 
+@defun main-thread-p &optional thread
+This function returns non-@code{nil} if @var{thread} is the main
+thread.  If @var{thread} is @code{nil} or omitted, it defaults to the
+current thread.
+@end defun
+
 @defun all-threads
 Return a list of all the live thread objects.  A new list is returned
 by each invocation.
--- etc/NEWS~	2018-03-14 06:39:58.000000000 +0200
+++ etc/NEWS	2018-06-05 17:37:13.301233500 +0300
@@ -361,6 +361,11 @@
 * Lisp Changes in Emacs 27.1
 
 +++
+** New primitive 'main-thread-p'.
+This can be used in code which needs to work differently when it runs
+in threads other than the main thread.
+
++++
 ** New function assoc-delete-all.
 
 ** 'print-quoted' now defaults to t, so if you want to see

Message received at control <at> debbugs.gnu.org:

Received: (at control) by debbugs.gnu.org; 21 Jun 2018 11:28:48 +0000
From debbugs-submit-bounces <at> debbugs.gnu.org Thu Jun 21 07:28:48 2018
Received: from localhost ([127.0.0.1]:58270 helo=debbugs.gnu.org)
	by debbugs.gnu.org with esmtp (Exim 4.84_2)
	(envelope-from <debbugs-submit-bounces <at> debbugs.gnu.org>)
	id 1fVxlg-0001ol-3b
	for submit <at> debbugs.gnu.org; Thu, 21 Jun 2018 07:28:48 -0400
Received: from mail-io0-f182.google.com ([209.85.223.182]:35461)
 by debbugs.gnu.org with esmtp (Exim 4.84_2)
 (envelope-from <npostavs@HIDDEN>) id 1fVxlc-0001oW-Az
 for control <at> debbugs.gnu.org; Thu, 21 Jun 2018 07:28:44 -0400
Received: by mail-io0-f182.google.com with SMTP id q4-v6so2661257iob.2
 for <control <at> debbugs.gnu.org>; Thu, 21 Jun 2018 04:28:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
 h=from:to:subject:date:message-id:mime-version;
 bh=nc7XsPever8YcVJugZWtPzTVwkIsP3iI7h2BEpEF6QM=;
 b=KaglCdaEGMaAObLssk58hNXVT4ufDGEtHziWTNYzQNdwqa9QQgTfYF61XcMZKJhFYS
 dqUYwPN3dxfImc7OJq81w3KzRkSD3n6aJy1j4N587BZsNdsalqyIobwD5v5zuhfjy2RE
 jVE9+UeWp05BwwAHvnju8QvIqUGILDphjdQkGmT2B2D9lkBKkS2LGYGnMd0gYmoxPmq6
 2uNz0B1dAvLA0BAVfBUB7fRB97KMa7To9l4PFI8m8J6USJohZMbf6Fbs1pfdgNSa9mVn
 c+Sryc4mN5bNxxuRre1WeZZLdrmTcQnozaiv5KAk+dKn4cYPf2TIBu4j+bT8S0hM5sgD
 vJKQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20161025;
 h=x-gm-message-state:from:to:subject:date:message-id:mime-version;
 bh=nc7XsPever8YcVJugZWtPzTVwkIsP3iI7h2BEpEF6QM=;
 b=IQaWFrHcpjhk46MVDSGqsyHBBmsKVr2/cmGBYM5lh0rnyurA4RoiYFkRa79UTz/5gr
 P4dmNz8mOnglDQheV+zlOnb7CK7VqPYsFFvmqxgowvQNGVa2pPMGAnmKyCAbZguNFCBQ
 jjUWgQZwrivm5wVSGqO06QPohHWd1LTGxU9yDRT1E117HaJ22GFGZ19DWVxJ3Kp6m88z
 6rjT2BbTpZvyHUwF1XlbK0Xe+4YV7Z0rsKzD9/Yx/bXettcaROHIJIBR2eIacVUr4j3H
 +jLo0zty0TinbbA2P2pbe9LQDa4dRATN6+iBLHiiLpNG9HO9TaORrqaRlFl2fgwYXK1Y
 wDFA==
X-Gm-Message-State: APt69E0IrzSihmDBGlzzZmsqmai29govpMvrLZA/NhhYDei8uTjjayCU
 FsNhjDErjiZ/wDLYiwtBcABHfQ==
X-Google-Smtp-Source: ADUXVKI61IY+PYVPmwCnHd4kdAauYQEAytZVvT2ynaF8eYs5RbRDEh03gZIAbaeY6GWEfSAykEcp0g==
X-Received: by 2002:a6b:d40c:: with SMTP id
 l12-v6mr20771439iog.37.1529580518638; 
 Thu, 21 Jun 2018 04:28:38 -0700 (PDT)
Received: from zebian (cbl-45-2-119-34.yyz.frontiernetworks.ca. [45.2.119.34])
 by smtp.googlemail.com with ESMTPSA id
 h81-v6sm844287ith.2.2018.06.21.04.28.37 for <control <at> debbugs.gnu.org>
 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256);
 Thu, 21 Jun 2018 04:28:37 -0700 (PDT)
From: Noam Postavsky <npostavs@HIDDEN>
To: control <at> debbugs.gnu.org
Subject: control message for bug #31671
Date: Thu, 21 Jun 2018 07:28:36 -0400
Message-ID: <87y3f8qsyj.fsf@HIDDEN>
MIME-Version: 1.0
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Debbugs-Envelope-To: control
X-BeenThere: debbugs-submit <at> debbugs.gnu.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: <debbugs-submit.debbugs.gnu.org>
List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe>
List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/>
List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org>
List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help>
List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe>
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
X-Spam-Score: -1.0 (-)

tags 31671 + confirmed
quit

Last modified: Mon, 25 Nov 2019 12:00:02 UTC

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997 nCipher Corporation Ltd, 1994-97 Ian Jackson.