-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Add C callback in r_bp #946
Comments
@jduck your thoughts? |
I'll take this into consideration surely. |
After thinking some more about the issue, I think it's quite doable to have a callback function that gets called whenever a breakpoint is hit. That said, such a thing is only useful when using the r_debug API directly via C or bindings, right? In all likelihood the code would be executed right before "cmd.bp" is executed, so it wouldn't exactly be async. If something bad happens during processing of this breakpoint all bets would be off. For example, the user could kill the child or detach the inferior. If they do that, things are going to get really ugly when we attempt to proceed processing the breakpoint handling... |
yep. that callback will be only usable when using the api, but my idea was to use it interanlly because of those hairy corners
|
Luckily the handling of when breakpoints are hit is much simpler than continuing afterward. hehe. |
ping |
@jduck ping? |
Sorry, no time lately :-/ |
cc @leberus |
Used for tracing, breakpointing etc, and running code from inside the api. this will make the debugger loop async and we will require to add other callbacks to handle other exceptions instead of checking right after the
waitpid()
thingThe text was updated successfully, but these errors were encountered: