Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Breakpoint stuck on #48

Closed
michaelfavia opened this issue Feb 19, 2013 · 5 comments
Closed

Breakpoint stuck on #48

michaelfavia opened this issue Feb 19, 2013 · 5 comments
Labels
bug
Milestone
Version 1.4.0

Comments

@michaelfavia
Copy link

After adding a breakpoint and walking through the debugger I am unable to remove the breakpoint (f10) after i exit debugging with f6.

I am able to add and remove it with toggle f10 until I actuality use it as a stopping point.

Tested with master and dev branches.
@joonty
Copy link
Collaborator

joonty commented Feb 20, 2013

Hi, thanks for this, It looks like it's related to #43 - the fact that breakpoints sometimes can't be untoggled was raised as a secondary issue. I'll close that one and leave this issue open, as it's the primary issue here.

@joonty joonty mentioned this issue Feb 20, 2013
Closed
@joonty
Copy link
Collaborator

joonty commented Feb 28, 2013

Hi,

If you could give the dev branch a go this problem should be fixed.

Cheers

@qstrahl
Copy link
Collaborator

qstrahl commented Mar 5, 2013

Having experienced the same issue I can confirm that it is now fixed in dev.

@joonty joonty closed this as completed in 5fef790 Mar 6, 2013
@michaelfavia
Copy link
Author

Sorry for the delay. Tested in dev and it works as expected. Thank you.

@joonty
Copy link
Collaborator

joonty commented Mar 7, 2013

This is also now in 1.4.0.

joonty added a commit that referenced this issue Apr 4, 2013
@joonty
Allow removing of breakpoints after debugging, fix #48
01a97ae 
If set_line() was called on a breakpoint, the value was not cast to an
integer. This caused comparisons to fail. Now always wrap the value in
int().
joonty added a commit that referenced this issue Apr 6, 2013
@joonty
Allow removing of breakpoints after debugging, fix #48
dcc8e06 
If set_line() was called on a breakpoint, the value was not cast to an
integer. This caused comparisons to fail. Now always wrap the value in
int().
@Garethp Garethp mentioned this issue Jul 5, 2019
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
Version 1.4.0
Development

No branches or pull requests
3 participants
@michaelfavia @joonty @qstrahl