Re: [cdt-dev] CDT & Eclipse Automotive Industry Working Group

[<ken.ryall@xxxxxxxxx>]

EDC does have forked and improved versions of several of the parsers in
org.eclipse.cdt.core and some new ones that could find a home there. We
forked them because most are public API in that plug-in and we needed the
ability to revise them during EDC development without having to bump up
the major version of org.eclipse.cdt.core.

I'm glad you brought this up because we always intended to merge them back
into org.eclipse.cdt.core and this might be the right time to do that.
I'll do an inventory, it has been a while since I compared them.

- Ken

On 2/22/11 4:23 PM, "ext James Blackburn" <jamesblackburn@xxxxxxxxx> wrote:

>On 21 February 2011 10:38, Andreas Graf <andreas.graf@xxxxxxxxx> wrote:
>> Analysis of executables:
>> The problem
>> -We have lots of tools that read information from executables, debug
>> information, map files
>> -Different compilers generate different file formats or dialects
>> -Supporting a wide range of input formats for every tool is a lot of
>>effort
>> -We expect that every large scale embedded software development has
>> similar tools
>> -But very few are published ­ probably because they are so specific to a
>> problem or platform
>
>CDT.core has binary parsers for the platforms we support, including
>ELF, MachO, PE, XCoff with some support for extracting info from
>various debug info types: Dwarf Stabs.
>
>I believe EDC have re-written some of these from scratch to provide
>more information for their debugger. The binary parsers in EDC may be
>better than those we have in core and ideally we should unify them.
>Perhaps one of the EDC devs can fill us in on what changes there are
>and whether there's a plan to replace the existing binary parsers?
>
>Cheers,
>James
>
>> -The proposed solution
>> -Establish a standardized interface to decouple information providers
>> from consumers
>> -Individual information providing plugins for each compiler / platform
>> -Tools can be generic and easily published
>>
>> The idea would be to work on providing a plugin that provides the
>> functionality to get information out of ELF/DWARF/COFF/stabs et al. for
>> things like a memory layout viewer, code size analysis, address
>> extraction, component budget checks. etc.
>>
>> Has this already been addressed in any of the CDT discussions?
>>
>> Best Regards,
>>
>> Andreas
>>
>> --
>> Andreas Graf
>> Business Development Manager Automotive
>> Mobil: +49 (0) 151-10860479 (preferred)
>> Tel.: +49 (0) 711 / 34 21 91-0
>> Fax.: +49 (0) 711 / 34 21 91-29
>>
>>
>> Web: http://www.itemis.de
>> Mail: andreas.graf@xxxxxxxxx
>> Xing: http://www.xing.com/profile/Andreas_Graf
>> Twitter: http://www.twitter.com/grafandreas
>> Blog: http://5ise.quanxinquanyi.de
>>
>> itemis GmbH
>> Meitnerstr. 10
>> D-70563 Stuttgart
>> Rechtlicher Hinweis:
>> Amtsgericht Mannheim, HRB 50700996
>> Ust.Id.Nr.: DE250574762
>> Geschäftsführer: Sebastian Neus
>>
>> _______________________________________________
>> cdt-dev mailing list
>> cdt-dev@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/cdt-dev
>>
>_______________________________________________
>cdt-dev mailing list
>cdt-dev@xxxxxxxxxxx
>https://dev.eclipse.org/mailman/listinfo/cdt-dev