lurado / lldo Goto Github PK

1. Be able to write scripts
   • LLDB command to print the project path (parse source info)
   • LLDB command to take a project relative path to a directory containing .lldb files. Create alias <file> command source <file>.lldb for every file in that directory.
2. Write documentation
   • Create a breakpoint anywhere in your code
     • Swift:
       • a symbolic breakpoint in @objc <module>.<AppDelegate>.init (@objc LLDO.AppDelegate.init)
     • ObjC
       • In your main function: Symbol main in your module (LLDO)
       • In any implemented AppDelegate method
   • execute debugger command create_actions <path>. Depending on where you set your breakpoint, path might need be be adjusted (give or take a ..)

The parameter should still be a plain String and the current use cases should remain unchanged.

• https://gist.github.com/kastiglione/d7fc5b3b3ebab1248333b858591e06b0#file-lldbinit
• https://youtu.be/9Io2_W1iDLQ?t=1250
• https://github.com/kastiglione/lldb-helpers
• https://www.dropbox.com/s/9sv67e7f2repbpb/lldb-commands-map.png?dl=0
  • create bif => breakpoint if/condition (-F -> lldb-helpers)
  • create baction => breakpoint action (-o -> youtube)

"LLDO - Automation for LLDB"?

Like Chisel. That would give users an easy way to update or rather know when there's something to update.

Relevant documentation: https://docs.brew.sh/Formula-Cookbook