diff options
Diffstat (limited to 'gdb/macroscope.c')
| -rw-r--r-- | gdb/macroscope.c | 50 |
1 files changed, 25 insertions, 25 deletions
diff --git a/gdb/macroscope.c b/gdb/macroscope.c index 3b02c97..996a6c9 100644 --- a/gdb/macroscope.c +++ b/gdb/macroscope.c @@ -60,25 +60,25 @@ sal_macro_scope (struct symtab_and_line sal) else { /* There are, unfortunately, cases where a compilation unit can - have a symtab for a source file that doesn't appear in the - macro table. For example, at the moment, Dwarf doesn't have - any way in the .debug_macinfo section to describe the effect - of #line directives, so if you debug a YACC parser you'll get - a macro table which only mentions the .c files generated by - YACC, but symtabs that mention the .y files consumed by YACC. - - In the long run, we should extend the Dwarf macro info - representation to handle #line directives, and get GCC to - emit it. - - For the time being, though, we'll just treat these as - occurring at the end of the main source file. */ + have a symtab for a source file that doesn't appear in the + macro table. For example, at the moment, Dwarf doesn't have + any way in the .debug_macinfo section to describe the effect + of #line directives, so if you debug a YACC parser you'll get + a macro table which only mentions the .c files generated by + YACC, but symtabs that mention the .y files consumed by YACC. + + In the long run, we should extend the Dwarf macro info + representation to handle #line directives, and get GCC to + emit it. + + For the time being, though, we'll just treat these as + occurring at the end of the main source file. */ ms->file = main_file; ms->line = -1; complaint (_("symtab found for `%s', but that file\n" - "is not covered in the compilation unit's macro information"), - symtab_to_filename_for_display (sal.symtab)); + "is not covered in the compilation unit's macro information"), + symtab_to_filename_for_display (sal.symtab)); } return ms; @@ -111,16 +111,16 @@ default_macro_scope (void) else { /* Don't call select_source_symtab here. That can raise an - error if symbols aren't loaded, but GDB calls the expression - evaluator in all sorts of contexts. - - For example, commands like `set width' call the expression - evaluator to evaluate their numeric arguments. If the - current language is C, then that may call this function to - choose a scope for macro expansion. If you don't have any - symbol files loaded, then get_current_or_default would raise an - error. But `set width' shouldn't raise an error just because - it can't decide which scope to macro-expand its argument in. */ + error if symbols aren't loaded, but GDB calls the expression + evaluator in all sorts of contexts. + + For example, commands like `set width' call the expression + evaluator to evaluate their numeric arguments. If the + current language is C, then that may call this function to + choose a scope for macro expansion. If you don't have any + symbol files loaded, then get_current_or_default would raise an + error. But `set width' shouldn't raise an error just because + it can't decide which scope to macro-expand its argument in. */ struct symtab_and_line cursal = get_current_source_symtab_and_line (); |