Skip to content

What is the expected way to debug the native library? #29

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

Open
zahhak opened this issue Dec 26, 2017 · 2 comments
Open

What is the expected way to debug the native library? #29

zahhak opened this issue Dec 26, 2017 · 2 comments

Comments

@zahhak
Copy link

zahhak commented Dec 26, 2017

As the native library is usually spawned by a nodejs code located outside of this repository - what is the expected way to debug the calls to the spawned process?

@zahhak
Copy link
Author

zahhak commented Dec 26, 2017

I guess it is done by waiting with lldb for the process spawn process attach --name ios-device-lib --waitfor (this could be done from xcode in debug -> attach to process by PID or Name)

@Mitko-Kerezov
Copy link
Contributor

That would depend on what you'd like to debug.
If you'd like to debug the C++ code you could launch the binary directly and paste a message, connected to the section you'd like to debug manually. I've added some example messages in the docs.
If you'd like to debug the Node.js you could write a sample script that reproduces some behavior and debug it in VS Code.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants