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
When you load up ocamldebug, you have to supply module unique names/paths. It's pretty tricky to get right, especially when you namespace modules. But the good thing is that obuild has all the knowledge about original source locations, and their respective module names/compilation artifact names and can automatically generate a dirty simple debug start script that lets you start debugging any bytecode program instantly.
The text was updated successfully, but these errors were encountered:
Actually, I never use ocamldebug because of difficulty to start it, so it is an excellent idea.
Do you have a sample of a bootstrap file from a small project with one library ?
When you load up
ocamldebug
, you have to supply module unique names/paths. It's pretty tricky to get right, especially when you namespace modules. But the good thing is thatobuild
has all the knowledge about original source locations, and their respective module names/compilation artifact names and can automatically generate a dirty simple debug start script that lets you start debugging any bytecode program instantly.The text was updated successfully, but these errors were encountered: