brummett / Devel-hdb

A graphical Perl debugger implemented as a web service
31 stars 9 forks source link

execution did not terminate after the debugger terminated #36

Closed nnutter closed 11 years ago

nnutter commented 11 years ago

execution did not terminate after the debugger terminated

! perl -d:hdb=a foo.t
Using libraries at /gscuser/nnutter/genome/master/lib/perl/
Debugger pid 1091 listening on http://0.0.0.0:8080/
ok 1 - created TestResult class
not ok 2 - correctly failed to create an instance of $class_name with (something => undef)
#   Failed test 'correctly failed to create an instance of $class_name with (something => undef)'
#   at foo.t line 21.
1..2
# Looks like you failed 1 test of 2.
Removing remaining resource lock: '/gsc/var/lock/genome/TestResult/0ec3b32302a87e4d2ed444ba9661e572' at /gscuser/nnutter/genome/master/lib/perl/Genome/Sys/Lock.pm line 316.
Debugged program pid 1091 terminated with exit code 1

^CINT/TERM cleanup activated in Genome::Utility::Filesystem
 at /gscuser/nnutter/genome/master/lib/perl/Genome/Sys/Lock.pm line 310.
        Genome::Sys::Lock::INT_cleanup('INT') called at /usr/lib/perl/5.10/IO/Socket.pm line 236
        eval {...} called at /usr/lib/perl/5.10/IO/Socket.pm line 236
        IO::Socket::accept('IO::Socket::INET=GLOB(0x3ebf670)') called at /usr/share/perl5/Devel/hdb/Server.pm line 30
        Devel::hdb::Server::accept_loop('Devel::hdb::Server=HASH(0x3ebf118)', 'CODE(0x401e2b8)') called at /usr/share/perl5/HTTP/Server/PSGI.pm line 59
        HTTP::Server::PSGI::run('Devel::hdb::Server=HASH(0x3ebf118)', 'CODE(0x401e2b8)') called at /usr/share/perl5/Devel/hdb/App.pm line 673
        Devel::hdb::App::run('Devel::hdb::App=HASH(0x401e120)') called at /usr/share/perl5/Devel/hdb/DB.pm line 186
        DB::DB called at /usr/share/perl5/Devel/hdb/DB.pm line 422
        DB::fake::at_exit() called at /usr/share/perl5/Devel/hdb/DB.pm line 416
        DB::END() called at foo.t line 0
        eval {...} called at foo.t line 0
END failed--call queue aborted.
nnutter commented 11 years ago

Now I understand what I missed so this should maybe just be classified as "could be better" but that's a matter of opinion. The problem ended and I got a popup saying it ended but I still needed to dismiss that popup and then click Exit as well. I believe that's how the command line debugger works as well so I guess it could be better if you added an exit button to the program terminated popup.

brummett commented 11 years ago

fixed in 31b9b52