Skip to content

Fix "usueful" typo #272

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
mattip merged 1 commit into from
Sep 23, 2025
Merged

Fix "usueful" typo #272

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/vmprof.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -191,7 +191,7 @@ As most statistical profilers, the core idea is to have a signal handler which
periodically inspects and dumps the stack of the running program: the most
frequently executed parts of the code will be dumped more often, and the
post-processing and visualization tools have the chance to show the end user
usueful info about the behavior of the profiled program. This is the very same
useful info about the behavior of the profiled program. This is the very same
approach used e.g. by `gperftools`_.

However, when profiling an interpreter such as CPython, inspecting the C stack
Expand Down
Loading