Lines Matching refs:with

3 Debugging xnu through kernel core files or with a live device.
7 xnu’s debugging macros are compatible with both Python 3.9+. Please be careful about pulling
18 * Name collisions at the top level may override methods with unexpected results.
29 ### Dealing with binary data
46 with open(filepath, 'wb') as f:
57 with open(filepath, 'wb') as f:
82 provides you with buffering (aka caching) in case your random small chunk accesses are repeated:
112 with strange characters in it. The lossless option is meant to be used when a string is only a tran…
126 ### Dealing with signed numbers
157 Ensure the macro matches what LLDB returns from the REPL. For example, compare `showproc(xxx)` with…
160 # 1. Run LLDB with debug options set
181 # 2. Grab symbols with dsymForUUID
184 # 3. Run lldb with local symbols to avoid dsymForUUID NFS
189 The actual steps are identical to previous testing. Run of a macro to different file with `-o <outf…
201 * Even with coredumps, testing the macros takes too long in our automation system and triggers the
207 Install **coverage** lib with:
216 # 1. Start LLDB with your macros as described above.
297 The easiest way to debug an exception is to re-run your macro with the `--debug` option.
303 To report an actionable radar, please use re-run your failing macro with `--radar`.
308 ### Debugging with pdb
316 Problem: Something wrong is going on with addkext macro. What now?
331   2. Use interactive mode and invoke functions with arguments directly.
333 After inspecting addkext macro code and calling few functions with arguments directly we can see th…
363 Lets try to look around with a debugger.
368 	# Run last statement with debugger.