This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 148706 - [65cat] [core] Cancelling debugger requires two stops.
Summary: [65cat] [core] Cancelling debugger requires two stops.
Status: NEW
Alias: None
Product: ruby
Classification: Unclassified
Component: Debugger (show other bugs)
Version: 6.x
Hardware: PC Linux
: P3 blocker (vote)
Assignee: issues@ruby
URL:
Keywords:
: 172895 (view as bug list)
Depends on:
Blocks:
 
Reported: 2008-09-30 08:47 UTC by esmithbss
Modified: 2011-01-28 20:12 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description esmithbss 2008-09-30 08:47:28 UTC 
[ BUILD # : 200809290201 ]
[ JDK VERSION : 1.6.0_07 ]

When debugging a Ruby process, just clicking on the stop button in
the debug toolbar doesn't shut down the debugger process.  I need to
go to the tasks running at the bottom of the window and shutdown the
debugger there as well.
Comment 1 esmithbss 2008-10-01 02:33:06 UTC 
This just happened to me again.  This time on 200809300201.  However, this time it appears that the debugger never
completely launched.  This is leading me to believe it may be a timeout issue where the IDE expects the debugger to
start within x seconds, but it is taking too long.  When x seconds passes, the IDE tries to kill the debugger and
detaches.  But the process is still running (somehow) in the background so it shows in the tasks (bottom right corner)
and is still in the process table for the OS.
Comment 2 esmithbss 2008-10-05 05:13:29 UTC 
I believe I have steps to reproduce.

1) Set a breakpoint in the application.

2) Start a debugging session

3) When the system stops at the breakpoint, step through 1 or 2 steps.

4) Stop the debugger session using the stop button in the toolbar. -- At this point, the IDE drops the connection to the
debugger at the toolbar, but the debugger is still running and is shown in the bottom right corner.

5) Now select "Cancel Process" in the process monitor at the bottom right of the IDE. -- At this point, the debugger
still isn't quite cancelled.

6) To actually kill the debugger now that the IDE has been 'disconnected' from it, go to the command line or other OS
level process monitoring system and kill the debugger process.

As you can see, it is expected that the debugger will stop at #4, but if not, it should stop at #5.  There is no reason
we should have to go to #6 to kill the debugger.
Comment 3 Martin Krauskopf 2008-10-09 12:43:29 UTC 
Sorry for delay, was on vacation........

I'm not able to reproduce however. Tried with the latest build on Linux with bundled JRuby and MRI with, simple Ruby
script. Did you have some other configuration or did you use Rails application? Might be help would help, not sure:

  http://wiki.netbeans.org/RubyDebugging#section-RubyDebugging-HowToFileABug
Comment 4 Erno Mononen 2009-10-01 16:00:29 UTC 
*** Issue 172895 has been marked as a duplicate of this issue. ***
Comment 5 Tomas Danek 2009-10-19 11:49:25 UTC 
100% reproducible on my Vista box.
- simple script, started jruby debugger, it stopped at BP
- killed debugging process by stop button on output window
- process was not killed (program counter in editor window, as well as java process in task manager)
Comment 6 Tomas Danek 2009-10-19 11:50:31 UTC 
just let me know how can i help do hunt this...would logging help?