RE: [cdt-dev] Issues with unit tests for CDT 1.2.1 RC1

["Tumashov, Sergey" <sergey.tumashov@xxxxxxxxx>]

	Hi, Alain!

Thanks for your response! I'm running the tests on a single P4 processor under Red Hat EL Workstation 3 using Sun 1.4.2 JVM.
I've checked the tools you wrote about (addr2line/c++filt) and I found that they present in my path. So it doesn't seem to be the reason. But I did the following: I checked out a subsequent revision (1.3) of org.eclipse.cdt.core.model.tests.BinaryTests from CVS. The revision I used before was 1.2 tagged with CDT_1_2_1_RC1. The later revision differs by some addition in the code of the setUp method. As I could understand it the addition replaces the default binary parser used by CCorePlugin by GNUElfParser, which is able to extract debug symbols from binaries as it is seen from the comment. After I built the test plugin with the newer revision of BinaryTests the testGetChildren method started to work correctly and now all of 560 core tests pass successfully. Alain, I'm not sure that the decision I applied is absolutely correct - it more looks like a kind of hack. But it makes me think that in the future final release of CDT 1.2.1 the problem with BinaryTests.testGetChildren() is going to disappear.
Well, I'll work more on the second issue with LocationTests.testIsEquals and if I find something I'll post it here.

Regards,
	Sergey

-----Original Message-----
From: cdt-dev-admin@xxxxxxxxxxx [mailto:cdt-dev-admin@xxxxxxxxxxx]On Behalf Of Alain Magloire
Sent: Wednesday, February 18, 2004 12:29 AM
To: cdt-dev@xxxxxxxxxxx
Subject: Re: [cdt-dev] Issues with unit tests for CDT 1.2.1 RC1


> 
> 	Hi, Alan!
> 
> 	Thank you for your response! Could you please make it more certain? =
> What does the term "GNU toolchain" stand for? If you mean the whole set =
> of tools including gcc, gdb, binutils, and ld, then it cannot be the =
> reason of the problem since I have each of them installed. Though I'm =
> not an expert in linux programming and I may have ovelooked something..
> 

You need "addr2line" in your path.

The tests are using precompiled Elf objects/excutable, that we know
as certain symbols etc ..

Now things seem to work fine here ...but ...
So on what machine are you running the tests?


_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/cdt-dev