Testing Call frame information in .debug_frame section

Petr Hluzín petr.hluzin@gmail.com
Tue Feb 15 22:13:00 GMT 2011


On 15 February 2011 19:02, Richard Henderson <rth@redhat.com> wrote:
> On 02/15/2011 09:41 AM, Richard Henderson wrote:
>> On 02/13/2011 07:10 AM, Petr Hluzín wrote:
>>> http://xfree86.cygwin.ru/ml/binutils/2010-08/msg00109.html
>>
>> I'll agree that a better error message would be helpful.
>
> Committed as follows.
>
>
> r~
>
>
>        * dw2gencfi.c (dot_cfi_dummy): New.
>        (cfi_pseudo_table) [!TARGET_USE_CFIPOP]: New.
>        * read.c (pobegin): Unconditionally call cfi_pop_insert.
>

Great, thanks.

Note: The submitted code code does not print the platform GAS is
configured for. If makefile/IDE is accidentally launching wrong build
of GAS then user will have hard time figuring this out. If it is not
an accident then the extra information is useful for googling since
recovery steps may be different. ("CFI on arch FOO? You have to
upgrade to version XY" vs "CFI on arch BAR? You have to apply this
patch.")

-as_bad (_("CFI is not supported for this target"));
+as_bad (_("CFI is not supported for target '" TARGET_FORMAT "'"));

Also "intelligable" looks like a typo. Perhaps "intelligible"?

-- 
Petr Hluzin



More information about the Binutils mailing list