|
26 | 26 | * [Cleaning up](#cleaning-up)
|
27 | 27 | * [Inspecting and Manupulating Files in an Indexed Project](#inspecting-and-manupulating-files-in-an-indexed-project)
|
28 | 28 | * [Debugging and Diagnosing](#debugging-and-diagnosing)
|
| 29 | + * [Profiling](#profiling) |
| 30 | + * [Post-mortem debugging](#post-mortem-debugging) |
29 | 31 | * [Shell Completion](#shell-completion)
|
30 | 32 | * [Hardware Acceleration](#hardware-acceleration)
|
31 | 33 | * [For Developers](#for-developers)
|
@@ -551,6 +553,21 @@ VECTORCODE_LOG_LEVEL=INFO vectorcode vectorise file1.py file2.lua
|
551 | 553 | > Depending on the MCP/LSP client implementation, you may need to take extra
|
552 | 554 | > steps to make sure the environment variables are captured by VectorCode.
|
553 | 555 |
|
| 556 | +#### Profiling |
| 557 | +
|
| 558 | +When you pass `--debug` parameter to the CLI, VectorCode will track the call |
| 559 | +stacks with [cprofile](https://docs.python.org/3/library/profile.html). The |
| 560 | +stats will be saved to the log directory mentioned above. You may use an |
| 561 | +external stats viewer (like [snakeviz](https://jiffyclub.github.io/snakeviz/)) |
| 562 | +to load the profiling stats for a better viewing experience. |
| 563 | +
|
| 564 | +#### Post-mortem debugging |
| 565 | +
|
| 566 | +VectorCode can work with [coredumpy](https://github.com/gaogaotiantian/coredumpy) |
| 567 | +to snapshot an exception so that developers can inspect the error |
| 568 | +asynchronously. To use this, you'd need to install the `vectorcode[debug]` |
| 569 | +dependency group: `uv tool install vectorcode[debug]`. |
| 570 | + |
554 | 571 | ## Shell Completion
|
555 | 572 |
|
556 | 573 | VectorCode supports shell completion for bash/zsh/tcsh. You can use `vectorcode -s {bash,zsh,tcsh}`
|
|
0 commit comments