luxolus/pyo3
2
0
Fork 0
Code Issues Pull requests Packages Projects Releases Wiki Activity

Fix some typos in user guide

Browse source
This commit is contained in:
Alexander Niederbühl 2019-03-13 17:14:17 +01:00
parent a9e78b98d1
commit 310e597693
2 changed files with 5 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
guide/src/advanced.md
View file

@ -2,6 +2,6 @@
## ffi
pyo3 exposes much of python's c api through the `ffi`.
pyo3 exposes much of python's C api through the `ffi`.
The c api is naturually unsafe and requires you to manage reference counts, errors and specific invariants yourself. Please refer to the [C API Reference Manual](https://docs.python.org/3/c-api/) and [The Rustonomicon](https://doc.rust-lang.org/nightly/nomicon/ffi.html) before using any function from that api.
The C api is naturally unsafe and requires you to manage reference counts, errors and specific invariants yourself. Please refer to the [C API Reference Manual](https://docs.python.org/3/c-api/) and [The Rustonomicon](https://doc.rust-lang.org/nightly/nomicon/ffi.html) before using any function from that api.

6
guide/src/debugging.md
View file

@ -20,9 +20,9 @@ See [cargo expand](https://github.com/dtolnay/cargo-expand) for a more elaborate
## Running with Valgrind
Valgrind is a tool to detect memory managment bugs such as memory leaks.
Valgrind is a tool to detect memory management bugs such as memory leaks.
You first need to installa debug build of python, otherwise valgrind won't produce usable results. In ubuntu there's e.g. a `python3-dbg` package.
You first need to install a debug build of python, otherwise valgrind won't produce usable results. In ubuntu there's e.g. a `python3-dbg` package.
Activate an environment with the debug interpreter and recompile. If you're on linux, use `ldd` with the name of you're binary and check that you're linking e.g. `libpython3.6dm.so.1.0` instead of `libpython3.6m.so.1.0`.
@ -37,4 +37,4 @@ The best start to investigate a crash such as an segmentation fault is a backtra
* Link against a debug build of python as described in the previous chapter
* Run `gdb <my-binary>`
* Enter `r` to run
* After the crash occured, enter `bt` or `bt full` to print the stacktrace
* After the crash occurred, enter `bt` or `bt full` to print the stacktrace