This is the mail archive of the
frysk@sourceware.org
mailing list for the frysk project.
Re: frysk-imports/lib/elf ChangeLog tests/TestElf.java
- From: Phil Muldoon <pmuldoon at redhat dot com>
- To: frysk at sourceware dot org
- Date: Thu, 12 Jul 2007 22:07:12 -0500
- Subject: Re: frysk-imports/lib/elf ChangeLog tests/TestElf.java
- References: <20070712185956.9810.qmail@sourceware.org>
Modified files:
lib/elf : ChangeLog
lib/elf/tests : TestElf.java
Log message:
2007-07-12 Phil Muldoon <pmuldoon@redhat.com>
* tests/TestElf.java (testCore): Deleted
(testElfCorePrpsNotes): Deleted.
(testElfCorePrstatusNotes): Deleted.
(testElfCorePrAuxvNotes): Deleted.
(testCore_x86): New. Rewritten from old version
to test cross ISA situations
(testElfCorePrpsNotes_x86): Ditto.
(testElfCorePrstatusNotes_x86): Ditto.
(testElfCorePrAuxvNotes_x86): Ditto.
(testCore_x8664): Ditto.
(testElfCorePrpsNotes_x8664): Ditto.
(testElfCorePrstatusNotes_x8664): Ditto.
(testElfCorePrAuxvNotes_x8664): Ditto.
This patch concludes the Elf sections of the core file test change.
There are now two sets of each test, one for each corefile. This covers
(at least core file elf access) the following scenarios depending on the
test hardware matrix the tests are executed on.
Tests on a 32 bit platform:
32 bit core file on 32 bit platform
64 bit core file on 32 bit platform
Little endian core files on a little endian system
Big endian core files on a little endian system
Tests on a 64 bit platform:
32 bit core file on 64 bit platform
64 bit core file on a 64 bit platform
Little endian core files on a big endian system
Big endian core files on a big end system
Additionally the tests now test multiple-thread core files more
thoroughly, checking all the registers in each thread for sanity as well
as checking for existence of corresponding floating point data. This is
in addition to the usual and existing note tests that existed before.
The second step is to phase out usage of the old, very simple
"test-core" core file in frysk-core, and translate those tests to use
the more complex and demanding new corefiles that were checked in last
week. At that time, the old test-core can be deleted.
Regards
Phil