This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: [6.0] PROBLEMS and NEWS
- From: Jim Blandy <jimb at redhat dot com>
- To: Andrew Cagney <ac131313 at redhat dot com>
- Cc: gdb-patches at sources dot redhat dot com
- Date: 22 Sep 2003 17:13:09 -0500
- Subject: Re: [6.0] PROBLEMS and NEWS
- References: <3F6CBFA5.7060308@redhat.com> <3F6F499E.7020102@redhat.com>
Looks good, just some picky comments:
Andrew Cagney <ac131313@redhat.com> writes:
> +* New back-trace mechanism (includes DWARF 2 Call Frame Identification).
> +
> +DWARF 2's Call Frame Identification makes available compiler generated
s/Identification/Information/; that's what the spec calls it.
> +information that more exactly describes the program's run-time stack.
> +By using this information, GDB is able to provide more robust stack
> +back-traces.
The GDB manual uses "backtrace" throughout, never "back-trace". There
are other uses of "back-trace" in the proposed text.
> +* DWARF 2 Location Expressions
> +
> +DWARF 2 Location Expressions allow the compiler to more exactly
> +describe the location of variables to the debugger.
It'd be nice to give some indication of why the user would care about
this, like: "Taken together with Dwarf 2 Call Frame Information,
location expressions give GDB the information it needs to debug
optimized code much more effectively."