From: Francois Gouget fgouget@free.fr
--- dlls/dbghelp/dbghelp_private.h | 4 ++-- dlls/dbghelp/dwarf.c | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/dlls/dbghelp/dbghelp_private.h b/dlls/dbghelp/dbghelp_private.h index a5ea41ae014..5e63d949a43 100644 --- a/dlls/dbghelp/dbghelp_private.h +++ b/dlls/dbghelp/dbghelp_private.h @@ -271,11 +271,11 @@ struct symt_data * address in one of its ranges * * Notes: - * (A): shall evolve but storage is native is awkward: from PGO testing, the + * (A): shall evolve but storage in native is awkward: from PGO testing, the * top function is stored with its first range of address; all the others * are stored as blocks, children of compiland, but which lexical parent * is the top function. This breaks the natural assumption that - * children <> lexical parent is symetrical. + * children <> lexical parent is symmetrical. * (B): see dwarf.c for some gory discrepancies between native & builtin * DbgHelp. */ diff --git a/dlls/dbghelp/dwarf.c b/dlls/dbghelp/dwarf.c index f8b3f8d717c..f9ffa374dbc 100644 --- a/dlls/dbghelp/dwarf.c +++ b/dlls/dbghelp/dwarf.c @@ -2201,7 +2201,7 @@ static void dwarf2_parse_subprogram_block(dwarf2_subprogram_t* subpgm, }
/* Dwarf tends to keep the structure of the C/C++ program, and emits DW_TAG_lexical_block - * for every block in source program. + * for every block the in source program. * With inlining and other optimizations, code for a block no longer lies in a contiguous * chunk of memory. It's hence described with (potentially) multiple chunks of memory. * Then each variable of each block is attached to its block. (A) @@ -2217,7 +2217,7 @@ static void dwarf2_parse_subprogram_block(dwarf2_subprogram_t* subpgm, * * DbgHelp only exposes a contiguous chunk of memory for a block. * - * => Store internaly all the ranges of addresses in a block, but only expose the size + * => Store internally all the ranges of addresses in a block, but only expose the size * of the first chunk of memory. * Otherwise, it would break the rule: blocks' chunks don't overlap. * Note: This could mislead some programs using the blocks' address and size information.