Stopping Erlang launches
- disconnect the console
- stop the backend (non-managed should only be removed from project's references)
Also, when doing q(). in the console, the backend goes down without quitting the LC
Likewise, when stopping backend in debugger ui, the LC is still running and "orphaned", it can't be killed.
- stop the backend (non-managed should only be removed from project's references)
Also, when doing q(). in the console, the backend goes down without quitting the LC
Likewise, when stopping backend in debugger ui, the LC is still running and "orphaned", it can't be killed.
Leave a comment
on 2008-08-28 20:06 *
By Vlad Dumitrescu
(Comment removed)
on 2008-10-09 09:55 *
By Vlad Dumitrescu
Description changed from How do we know when to remo... to - disconnect the console
-...
Summary changed from notification for "stopped" launch configs to Stopping Erlang launch configs
Remaining hours set to 20
Description changed from How do we know when to remo... to - disconnect the console
-...
Summary changed from notification for "stopped" launch configs to Stopping Erlang launch configs
Remaining hours set to 20
on 2009-02-05 12:10 *
By jakobc
Assigned to set to jakobc
Component changed from None to debugger
Description changed from - disconnect the console
-... to - disconnect the console
-...
Milestone changed from backlog to 0.4.5
Priority changed from Normal (3) to High (2)
Status changed from New to Accepted
Assigned to set to jakobc
Component changed from None to debugger
Description changed from - disconnect the console
-... to - disconnect the console
-...
Milestone changed from backlog to 0.4.5
Priority changed from Normal (3) to High (2)
Status changed from New to Accepted