You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
What is the expected way to debug the native library? #29
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?
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)
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.
Activity
zahhak commentedon 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 commentedon Dec 29, 2017
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.jsyou could write a sample script that reproduces some behavior and debug it in VS Code.