[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cdt-core-dev] Re: New elf magic numbers
|
>
> Alain,
>
> Thanks for that. It would be great in future to be able to add these
> numbers programmatically, rather than having to have them hard coded in
> this class.
Agreed.
> On a related note it would certainly be useful to us to be
> able to influence the name of the GNU tool that gets run by the utility
> classes such as CPPFilt and Addr2Line, since our executables have
> different names.
Actually it is possible. The Elf class should not call this
directly and the calls you are seing in Elf.java will be remove
We move the functionnality in the Binary Parser (IBinaryParser). For example in the
Std Make project you can set in the property the name of tools you want.
I believe for the ManagedBuilder it is set by builder(i.e. hardcoded).
> If we could provide those names and also the
> environment to run them in, then we could remove a large quantity of
> duplicate code in our release which is simply copied from the CDT source
> with very minor modifications. =20
>
The environment ... if you asking for generic way to set the environment
when spawning within the CDT ...
> Does anyone have any comments/objections to this? I'm happy to have a
> go at producing a patch for these features if they seem useful.
Take a look at GNUElfParser, CygwinPEParser, IBinaryParser before
it may do what you need. For example, QnX provides it "QNXBinaryParser"
who calls special version of "addr2line" etc ...
