I'm using spyder 3.3.6 and, since a week ago or so, the debugger has suddenly start ignoring any breakpoints I define by placing a red dot with a double click on the corresponding line. Once I start debugging pressing Ctrl+5 the debugger stops at the first line of the code, even if there isn't a breakpoint. Then when I press Ctrl+12 to move to the next breakpoints the debugger just ignores them and terminates the process without showing any error message.
Have a look at the screenshot to get a better idea of the problem:
Any suggestion to fix this?
Thanks.
Related
Somehow, after a vscode update my debug line-highlighting line is gone. Debugging works normal, but I never see the correct debugging line. The grey highliting in the screen below is just the cursor-line highlighting.
In the picture below, current debug position is line 147 - but no yellow debug line.
When i press F5, the next line gets highlighted grey, because the cursor switches there. But still no yellow highlight for my currently debuged line. When i click on on another line in the code the grey line switches to that position, leaving the current debug line without any highlighting.
I have a skin installed, "Solarized Express Soda", but deactivation does not fix this.
Is it possible to switch vscode versions back to test this further? Or to deactivate all extentions at once to have a vanilla vscode to approach the problem via elimination process?
VScode Version 1.46.1,
Node Version 10.21.0
Actually, i solved the problem now.
I installed a previous version of vscode, january 1.42.1 - Now it works again properly. I think i will report this issue on the vscode forums. Pherhaps an issue in correlation with my many extentions & old node version 10.21.0(which is still in need - thats another topic)
But perhaps, someone can tell me what I've done wrong, actually, i cant see anything wrong on my side here...
When debugging program in Idea (I'm using 14.1.5 Community Edition), it attempts to put the line I'm currently on close to the center of the screen. And it does so every single step. However, I find this default behavior very annoying, it looks like the code is jumping around.
I wonder if there a way to customize the debugger view in a way that the code would be fixed (as long as I'm not leaving one screen of code) and the current line highlighting would be moving around? (I didn't find it in the Debugger section of the settings.)
Many thanks.
You want to disable "Focus application on breakpoint" which is in the settings under Build,Execution, Deployment > Debugger - it's the first checkbox. It's help documentation reads:
If this check box is selected, on hitting a breakpoint, IntelliJ IDEA will show the location of this breakpoint in the editor and will attempt to bring its frame to the front.
This should do the trick.
I don't understand what's going on with the XCode debugger. I am using Xcode 3.1.2 and GCC 4.0 on 10.5. Sometimes, Occasionally, I test a C++ program, all active breakpoints become disabled. No breakpoints are taken - the program runs to completion. The dark blue breakpoint icons change to light blue or yellow with a blue border. Looking at the breakpoints list (CMD-Opt-B ) after the change, the breakpoints that were tagged with a checkmark are now tagged with a hyphen. (how do I get a "checkmark" icon with markdown?)
This is after they have been functioning normally. Sometime later, they will usually begin functioning normally again. I don't know what is responsible for either change. I have closed/reopened the debugger, files, and the full project. Most often, the proper beakpoint status is restored when I trivially change a source file and do a "Build & Debug" (Cmd-Y), but that doesn't always fix things
I have seen the reports of problems about "GLIBCXX_DEBUG_" here and elsewhere. That isn't my problem because I am using GCC 4.0, and don't use those flags. I have also seen reports of a similar problem with a really old XCode. Again, I don't believe that applies to me. Any ideas?
When the breakpoint markers turn yellow it means that you have more than one program being actively debugged by GDB. Try exiting all the programs except for the one you are currently debugging.
A yellow breakpoint symbol indicates the breakpoint is not loaded into the debugger. This can happen if you have more than one project running is what the previous answer was implying. Can also go yellow if you Run with breakpoints off instead of on.
This is occurring in Visual Studio 2005, in an ASP.NET Web Application.
For example, if I try to set a breakpoint in the following code:
if (frustrated)
{
bool cry = true;
} <-- breakpoint here
It will set the breakpoint on the indicator margin, but when I actually hit F5 to debug the application, the breakpoint will flicker on and off (the little red circle literally vanishes then reappears) before disappearing altogether. Other breakpoints will work, just not ones ending on a closing bracket. This used to work, until I installed then uninstalled ReSharper (either it broke it, or its just coincidence).
EDIT: Just to reiterate - this is something that used to work, but doesn't anymore. I know I can put the breakpoint on a different line, but this is not what I want to do. I want it to work normally again.
EDIT 2: Resetting all of my settings did not help.
Any ideas?
Set the breakpoint on the line above it, instead of a closing brace.
If the breakpoint turns from a solid circle to an empty circle it indicates that the breakpoint could not be set usually because of a mismatch between the code and the actual binary module being loaded. This can be fixed by building or rebuilding suspect modules.
All projects opened while ReSharper was installed were affected. I went through each project and deleted the .suo file. After that, life was good - I can set breakpoints again!
Often, when I have a breakpoint on some line in Visual Studio, The program will run and stop there. great. I will then click the red circle (or press F9) to remove it. Obviously I don't want my program to keep stopping there. The problem is that the next time I refresh the page the breakpoint is back! The only way to permanently remove it is to open the breakpoints window and remove it there. Why does this happen and how can I change this behavior?
I have noticed that these breakpoints which keep coming back have a little plus next to them in the breakpoints window which when you click on - open up many sub lines of breakpoints. What is the deal with that?
Thanks,
Adin
Helpful Key combo: to permanently delete all breakpoints, press CTRL + SHIFT + F9.
Just clear the breakpoint while the debugger is off. When you clear or add a breakpoint while debugging, the action only lasts for that debugging session.
The plus in the breakpoints window is there when one user-supplied breakpoint binds in multiple places. This can happen when a single file is loaded multiple times in the same debugging session, for example. The + lets you look at each of the places it bound.
#Joel: modifying breakpoints during a debugging session does not make your change temporary, although there are circumstances (like the original question), where the actual behavior can be non-obvious.
I've post suggestion to MS to fix it:
https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=391642
It appears since Visual Studio allows multiple breakpoints on a single line, i.e. in separate sub-clauses, architecturally it allows multiple identical breakpoints. The interface does not necessarily reflect this and you will see the removal of a breakpoint as graphically removing it, but not programmatically removing all instances of it.
Looking at the Debug > Windows > Breakpoints window shows for a given set of breakpoints on a line, they are stored in a sub-tree under that line item. Removing a breakpoint while watching this list will reveal the behaviour, that only one of a series of identical breakpoints is removed from the list associated with that line. By removing the breakpoint line item and with it all sub items it will completely remove all instances of the breakpoint.
Wipe the breakpoint out using the Breakpoints Window (Ctrl + Alt + B).
While debugging, when you hit the breakpoint, look at the BreakPoint window for the one that is bold.
Then, right-click it and choose Delete.