Re: [6.0] PROBLEMS and NEWS

[Andrew Cagney <ac131313@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.

Oops.

>> +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.

That will learn me for spellchecking it ...

>> +* 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."

At one stage I had the word optimized, but took it out.  I've changed it to:

DWARF 2 Location Expressions allow the compiler to more completly
describe the location of variables (even in optimized code) to the
debugger.

IA64 ABI, for instance,  specifies something other than CFI for doing 
unwinds so the LE <-> CFI link isn't that strong.

Andrew