Re: Forked processes && Perl TK Debugger (ptkdb)

I would like to try and resurrect this conversation. I have found this X11 limitation to be very frustrating. I am going to do a bit of investigation myself. Given that the standard Perl debugger has a hardcoded path for xterms (see https://metacpan.org/source/SHAY/perl-5.28.1/lib/perl5db.pl#L1335), there should be a way to integrate another X program, namely Devel::ptkdb.

Comment on Re: Forked processes && Perl TK Debugger (ptkdb)

Replies are listed 'Best First'.
Re^2: Forked processes && Perl TK Debugger (ptkdb) by LanX (Saint) on Apr 24, 2019 at 22:24 UTC
From what I remember are GUIs connected via a socket connection to the normal Perl debugger. The actions are just translated into normal debugger commands. That's at least how IDEs like Emacs connect to the debugging process and like tye already said debugging threaded programs should be supported by normal debugging. So If I were you I'd try to replicate the problem with the plain debugger ( `perl -d` ) and then an IDE like Komodo or Emacs. If these work, then the problem is most likely on the client side. Cheers Rolf _{(addicted to the Perl Programming Language :) Wikisyntax for the Monastery FootballPerl is like chess, only without the dice}	[reply] [d/l]

Replies are listed 'Best First'.

Re^2: Forked processes && Perl TK Debugger (ptkdb)
by LanX (Saint) on Apr 24, 2019 at 22:24 UTC

The actions are just translated into normal debugger commands.

That's at least how IDEs like Emacs connect to the debugging process and like tye already said debugging threaded programs should be supported by normal debugging.

So If I were you I'd try to replicate the problem with the plain debugger ( perl -d ) and then an IDE like Komodo or Emacs.

If these work, then the problem is most likely on the client side.

Cheers Rolf
_{(addicted to the Perl Programming Language :)

Wikisyntax for the Monastery
FootballPerl is like chess, only without the dice}

[reply]
[d/l]