RE: [cdt-dev] Problem with executing dsf-gdb JUnit tests

[sneha_apte <sneha_apte@xxxxxxxxxxxxxxxx>]

Hi All,

I was able to execute tests for gdb 6.8.
There was an issue related to 32 bit and 64 bit architecture compilation problems.
The class MultiThread.cc required 32 bit architecture due to which it failed to compile on my machine which is based on 64 bit architecture.
As a result, its exe was not generated.
This resulted in exception while executing most of the test cases which require MultiThread.exe.

To resolve this issue I had to add -m32 in GCC_FLAGS of data/launch/src/Makefile.
With this change, I faced no issues in test execution.

Results of tests for gdb 6.8:
On running 6.8 Test Suite we can observe 138 test cases with 1 failure.

Thank you all for your valuable inputs.

Thanks,
Sneha

-----Original Message-----
From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of John Cortell
Sent: Monday, March 08, 2010 7:06 PM
To: CDT General developers list.; CDT General developers list.
Subject: RE: [cdt-dev] Problem with executing dsf-gdb JUnit tests

At 03:19 AM 3/8/2010, sneha_apte wrote:
>As explained in the below link, after executing the
>JUnitPluginTests  for test suite 6.8, .exe files are generated and
>placed in data/launch/bin folder.
>These binaries seem to be generated for the .cc programs present in
>the data/launch/src folder (as given in theMakefile)
>No other binaries are seen to be generated.
>Thus it seems that binaries are not getting built for 6.8 tests.
>Is there are any step which I might be missing?

What other binaries are you expecting? Only one set of binaries are
supposed to be generated. There isn't going to be a set for each gdb version.


>As mentioned in below email, I debugged the code in class
>FinalLaunchSequence at the step that sends the command MIFileExecAndSymbol.
>For the package org.eclipse.cdt.test.dsf.gdb.tests, the code returns
>valid path for execPath variable and thus the command
>MIFileExecAndSymbol gets queued successfully.
>However for package org.eclipse.cdt.test.dsf.gdb.tests.tests_6_8
>the code does not get value for execPath and thus the command:
>MIFileExecAndSymbols is not queued.
>
>I had a doubt regarding the name of binary being specified. As per
>below mail,
>"The binary is specified in the @BeforeClass of each test
>by setting the ATTR_PROGRAM_NAME configuration attribute."
>
>Above mentioned configuration attribute is set in class ExampleTest
>of the package org.eclipse.cdt.test.dsf.gdb.tests.
>The @BeforeClass of tests in the 6.8 test package do not set the
>above mentioned attribute.
>
>Is the above mentioned observation expected?

The base class of each version-specific test class does. JUnit calls
the @BeforeClass of not only the class being tested but of its super
classes. The super class is called before the subclass.


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

DISCLAIMER
==========
This e-mail may contain privileged and confidential information which is the property of Persistent Systems Ltd. It is intended only for the use of the individual or entity to which it is addressed. If you are not the intended recipient, you are not authorized to read, retain, copy, print, distribute or use this message. If you have received this communication in error, please notify the sender and delete all copies of this message. Persistent Systems Ltd. does not accept any liability for virus infected mails.