@@ -229,7 +229,7 @@ pretty-printed IR into `build/ops.txt`. This is the final IR that
229
229
includes the output from exception and reference count handling
230
230
insertion passes.
231
231
232
- We also have tests that verify the generate IR
232
+ We also have tests that verify the generated IR
233
233
(` mypyc/test-data/irbuild-*.text ` ).
234
234
235
235
## Type-checking Mypyc
@@ -290,7 +290,7 @@ under `mypyc/lib-rt`.
290
290
291
291
## Inspecting Generated C
292
292
293
- It's often useful to inspect the C code genenerate by mypyc to debug
293
+ It's often useful to inspect the C code generated by mypyc to debug
294
294
issues. Mypyc stores the generated C code as ` build/__native.c ` .
295
295
Compiled native functions have the prefix ` CPyDef_ ` , while wrapper
296
296
functions used for calling functions from interpreted Python code have
@@ -386,7 +386,7 @@ Test cases can also have a `[out]` section, which specifies the
386
386
expected contents of stdout the test case should produce. New test
387
387
cases should prefer assert statements to ` [out] ` sections.
388
388
389
- ### Debuggging Segfaults
389
+ ### Debugging Segfaults
390
390
391
391
If you experience a segfault, it's recommended to use a debugger that supports
392
392
C, such as gdb or lldb, to look into the segfault.
@@ -409,7 +409,7 @@ Program received signal SIGSEGV, Segmentation fault.
409
409
```
410
410
411
411
You must use ` -n0 -s ` to enable interactive input to the debugger.
412
- Instad of ` gdb ` , you can also try ` lldb ` (especially on macOS).
412
+ Instead of ` gdb ` , you can also try ` lldb ` (especially on macOS).
413
413
414
414
To get better C stack tracebacks and more assertions in the Python
415
415
runtime, you can build Python in debug mode and use that to run tests,
0 commit comments