Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Add debugging documentation

See original GitHub issue

Currently we recommend that ndb is used to debug Exokit in the documentation, but that’s not commonly used. Instead most issues are related to native modules, were a native debugger is better.

We should update the documentation with a debugging guide accordingly. Even just pointers on how to bootstrap a debugging session for each platform would be useful.

Issue Analytics

State:
Created 4 years ago
Comments:5 (5 by maintainers)

Top GitHub Comments

1reaction

codingbyclcommented, May 7, 2019

Ok I will close and break out the new issues.

1reaction

avaercommented, May 7, 2019

That documentation still seems very fragmented and not tested, and isn’t covering how people actually debug. For example, on Windows, you’re probably using either Visual Studio or windbg, not MinGW.

Perhaps a better solution than documenting this smorgusbord of debuggers is delivering a better debugging solution in the studio, as well as a remote debugger for the mobiles.

And then document that functionality.