-
-
Notifications
You must be signed in to change notification settings - Fork 1
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
Debugger support #3
Comments
As of 48e34a0, basic debugging infrastructure has been installed. The nub thread currently doesn't do anything yet, neither does the debuggee after being debugged. To trace syscalls, Nevertheless, this is still enough to allow |
As of Specifically, |
As of
|
Have you used/reviewed Haiku's Debugger (i.e 'Debugger -c ') ?? Pros/Cons ?? |
I've used Haiku's As for HyClone, the debugger API is still incomplete. The most important feature that prevents Debugger from working is register reading support (it is not too hard to implement, simply reading the signal context will do the job), and probably thread stopping and resuming (which is also not too hard to implement, as we can simply send a signal to the target thread). |
For debugger support, Haiku uses specific syscalls that opens a magic port with the kernel.
The kernel also installs a "nub thread" to the debugged process.
How exactly this is done is still not documented. However, all of this should technically be possible using
ptrace
and/or signals.The text was updated successfully, but these errors were encountered: