unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Kari Pahula <kaol@iki.fi>
Cc: 18259@debbugs.gnu.org
Subject: bug#18259: 24.3; comint-interrupt-subjob fails to interrupt pthreaded programs
Date: Fri, 04 Dec 2020 12:28:49 +0100	[thread overview]
Message-ID: <874kl1kdxq.fsf@gnus.org> (raw)
In-Reply-To: <87ha1girv5.fsf@sammakko3.piperka.net> (Kari Pahula's message of "Wed, 13 Aug 2014 13:52:30 +0300")

Kari Pahula <kaol@iki.fi> writes:

> Trying to interrupt a debugged program in gud fails.  Pressing C-c C-c
> just displays "C-c C-cQuit" but nothing else happens.  This works in
> Emacs version 23.  It seems to me that Emacs 24 doesn't know how to
> signal stop to programs using pthreads.  The program in question is
> available at https://github.com/kaol/forcelayout
>
> (gdb) r
> Starting program: /home/kaol/src/forcelayout/forcelayout -i 1000 -r world-20140811.json picks-20140812.json world-20140812.json
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
> [New Thread 0x7ffff7308700 (LWP 14323)]
> [New Thread 0x7ffff6ab7700 (LWP 14324)]
> [New Thread 0x7ffff6266700 (LWP 14325)]
> [New Thread 0x7ffff5a15700 (LWP 14326)]
> [New Thread 0x7ffff51c4700 (LWP 14327)]
> [New Thread 0x7ffff4973700 (LWP 14328)]
> [New Thread 0x7ffff4122700 (LWP 14329)]
> [New Thread 0x7ffff38d1700 (LWP 14330)]
> [New Thread 0x7fffec645700 (LWP 14331)]
> [Thread 0x7fffec645700 (LWP 14331) exited]
>   C-c C-cQuit
> k
> (gdb) 

(This bug report unfortunately got no response at the time.)

I tried reproducing this bug with Emacs 28 -- by using gdb on Emacs
itself, which also uses pthreads, I think?  This seems to work fine for
me.  Are you still seeing this issue in more recent Emacs versions?

(gdb) r
Starting program: /home/larsi/src/emacs/trunk/src/emacs 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffeb6c8700 (LWP 167374)]
[New Thread 0x7fffeacbd700 (LWP 167375)]
[New Thread 0x7fffea273700 (LWP 167376)]
[Detaching after vfork from child process 167389]
[Detaching after vfork from child process 167390]
  C-c C-c[Thread 0x7fffeacbd700 (LWP 167375) exited]
[Thread 0x7fffeb6c8700 (LWP 167374) exited]
[Thread 0x7fffec5ea5c0 (LWP 167369) exited]
[Inferior 1 (process 167369) exited normally]
(gdb)


-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2020-12-04 11:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-13 10:52 bug#18259: 24.3; comint-interrupt-subjob fails to interrupt pthreaded programs Kari Pahula
2020-12-04 11:28 ` Lars Ingebrigtsen [this message]
2020-12-11 15:48 ` bug#18259: Interrupting pthreaded programs works again Kari Pahula

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=874kl1kdxq.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=18259@debbugs.gnu.org \
    --cc=kaol@iki.fi \
    /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).