Hidden breakpoints

Same here.

Plus (on the Mac) if I press the red stop button while the debugger is stopped within the code, the server won't shut down. And when you cancel the debugger will quit but there will be a rogue ruby process still running that prevents the server from starting up the next time.

Sorry I was no help...just wanted people to know more than one person is seeing this problem.

Mark

To stop, what you need to do is make sure the browser window with the running app is gone.  Also, what I generally do is have the Activity Monitor running, if need be, you can select the ruby process and kill it, then the RM dialog will go away.

Later, Guy

Hi guys,

What RubyMine version do you use? Do you try to debug several ruby applications simultaneously?

Regards,
Oleg

I have 2.01.  I can't seem to find a recreatable way to get it to happen, but I know that if I add/remove lines around a BP while I am in the debugger I can get it to happen.  I just played with it for a while here and got it to happen several times, but I couldn't get a set of steps that would lead to it happening.  Is there a file I can send you when there are hidden BP's?

Regards, Guy

I also have 2.0.1 (and now I'm using the 2.0.2 RC).

Yes...when the debugger is running and you are editing code where the break points are--especially adding additional lines in the file--some new hidden breakpoints get added. I usually stop the server and restart the debugger so as to get rid of any that show up.

Mark

Hi guys,

Could you please add these line to file idea.properties
ruby.debug.output=true

This will enable verbose output for ruby debugger, maybe console message will help to clarify the use case.

Regards,
Oleg

Thanks Oleg, I have a reproducible case and would like to get this resolved as it is a major pain in the rear.  I added the line to the file and now am wondering where I am supposed to be seeing the ruby console messages?  In the debug tab, console window?  I see nothing there.
Regards, Guy

Hi Guy,

Actually in the latest EAP build we've moved this setting to UI: File | Settings | Debugger | Ruby | Verbose debugger output.
Please enable this option, and you'll get ruby-debug verbose output within debug console window.

Regards,
Oleg

Ok, got it.  Attached is my dump.  I have added some lines to the dump that start with ***** and a note indicating what action I was taking.

I think the problem starts on line 268.  Notice that when I removed a line of code above the bp, it tells me it added bp #2 at line 191 (this was formerly line 192).  I only have one bp in the app, so shouldn't this be a modification of bp #1 rather than the addition of a new bp?  Then notice on line 272, when I deleted the bp, it deleted bp #2, but I believe there is still the mystery bp #1 sitting on the line 192 which was the original line that had a bp.  Follow?

If you need anything further let me know.

Thanks, Guy

I created a bug for this: http://youtrack.jetbrains.net/issue/RUBY-6385?projectKey=RUBY&query=%23gnicholas

Regards, Guy

Bump :)

This bug is really annoying...any chance of getting it fixed...please :)

Regards, Guy

Hi guys,

I've tried to reproduce it, however I didn't managed to do this yet. Could you please provide small code sample with steps to reproduce?

Regards,
Oleg

Happens to me all the time when debugging my application in mongrel.
It feels like when I am stopped at a breakpoint in line #27 then insert two lines before that (while still stopped at the breakpoint), then afterward I have a visible breakpoint at
line #29 and another invisible breakpoint at #27.

Stopping the application (while keeping RubyMine running) fixes this, but still it's very annoying.

(Build 96.886)


On 25.08.2010 19:44, Oleg Shpynov wrote:

Hi guys,

>

I've tried to reproduce it, however I didn't managed to do this yet. Could you please provide small code sample with steps to reproduce?

>

Regards,
Oleg

>

---
Original message URL: http://devnet.jetbrains.net/message/5270968#5270968

Put a BP in a controller.  Get to the BP, delete a line of code above the BP, hit save, run.  refresh, or whatever it takes to get back to the point where the BP is, clear the BP, and run.  Then refresh once again.  You should end up stopping where the BP was.

At the end of the log I provided earlier in this thread it seems fairly clear what the issue is.

I am stopped at a bp on line 192, and I delete a line of code above that line, this is what happens.  It is adding a BP named 2.  There is no deletion of the existing BP.
Processing: b  /Users/nicholas/Development/pulse/main/servers/pscom_site/app/controllers/application_controller.rb:191
<breakpointAdded no="2"  location="/Users/nicholas/Development/pulse/main/servers/pscom_site/app/controllers/application_controller.rb:191"/>

Then, when I delete the BP that is now on line 191, this gets called?  Again, there is still a dangling BP #1 that was my original BP.
Processing: delete 2
<breakpointDeleted no="2"/>

Regards, Guy

Thanks guys,

I've finally managed to reproduce this behavior.

We've recently fixed this problem, fix will be available in next EAP build.

Rockin'  Can't wait for the fix.

Thanks, Guy

Next Eap build is coming in several days.

I have no clue what is EAP
I am facing the same bug from RM 2.0.2 till 3.0.1
There are lots of ways how to get unremovable invisible breakpoint --
set a breakpoint somewhere, run, hit the breakpoint, -- edit -- and you got it
same stuf, hit the breakpoint make one step, providing that RM will freeze (yeps, -- happens) -- remove the breakpoint, run, refresh(or whatewer) to execute this code fragment again -- you have it again -- hidden breakpoint))))

No RM controls allow you to get rid from it -- disabling breakpoints, setting a breakpoint on the same line where hidden on appears to be and then removing it, etc -- nothing will work

In my case (WinXP) stopping debugger and launching it once again -- helps.
Yet this is very discomfortable and annoing (

--Yu.

Multiple hidden breakpoints in 3.0.1

Should you manage to make 1 hidden breakpoint and now go to that window which lists all the breakpoints = now ctrl+A, [remove] -- and all the breakpoints are hidden, yet debugger still stops on them.

... and this happened in the loop ((((((((((

... and restarting my debugger takes 5+min (there is thread, search for Tormoz keyword in the subject)