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.

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

Suspending after having stepped thru code does not work well #18

Open
borgdylan opened this issue Aug 7, 2014 · 3 comments
Open

Suspending after having stepped thru code does not work well #18

borgdylan opened this issue Aug 7, 2014 · 3 comments

Comments

@borgdylan
Copy link

I was trying to set a break point after having stepped thru code. I used Ctrl-c. SDB told me teh process was supsended but did not give the usual prompt. Pressing Ctrl-C again gives a warning and the prompt. However any command i type in does not get executed by SDB.

@alexrp
Copy link
Collaborator

alexrp commented Aug 21, 2014

So just to be clear, when you first pressed Ctrl-C, the process was already suspended? And pressing it put SDB into a bad state?

If so, I've seen that bug before, just haven't looked into it yet.

@alexrp alexrp self-assigned this Aug 21, 2014
@alexrp alexrp added this to the 2.0 milestone Aug 21, 2014
@borgdylan
Copy link
Author

When I pressed Ctrl-C the process was at a breakpoint.

@alexrp
Copy link
Collaborator

alexrp commented Jan 7, 2015

Hmm, I'm trying to repro this and I'm not having much luck.

Could you give me a test program and an exact set of steps to get SDB into this bad state?

@alexrp alexrp removed this from the 2.0 milestone Jan 8, 2018
@alexrp alexrp removed their assignment Apr 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants