This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: libgcj testsuite FAILs on Ubuntu
- From: Andrew Haley <aph at redhat dot com>
- To: Matthias Klose <doko at ubuntu dot com>
- Cc: java at gcc dot gnu dot org
- Date: Wed, 05 Aug 2009 12:12:17 +0100
- Subject: Re: libgcj testsuite FAILs on Ubuntu
- References: <4A7965CE.7080601@redhat.com> <4A794BFA.2060702@ubuntu.com>
Matthias Klose wrote:
> On 05.08.2009 12:58, Andrew Haley wrote:
>> There is a number of gcj stacktrace failures on Ubuntu ARM.
>>
>> They all look like this:
>>
>> StackTrace2$Inner.doCrash:FAIL - expected 33, got: 0, in file crtstuff.c
>> StackTrace2$Inner.foo:FAIL - expected 28, got: 0, in file crtstuff.c
>> StackTrace2.a:FAIL - expected 21, got: 0, in file crtstuff.c
>> StackTrace2.main:FAIL - expected 10, got: 0, in file crtstuff.c
>
> [...]
>
>> This is:
>>
>> Distributor ID: Ubuntu
>> Description: Ubuntu jaunty (development branch)
>> Release: 9.04
>>
>> I don't know how something as fundamental as dladdr() can possibly
>> fail and the system still appear to work, but there it is.
>
> Same on Debian, I don't see any difference in the failing testcase on
> Debian unstable (search for test-summary):
> https://buildd.debian.org/fetch.cgi?&pkg=gcj-4.4&ver=4.4.1-1&arch=armel&stamp=1248466701&file=log
Sorry, I just remembered that this test gets the PLT address, not the
address of the function. I'm cooking up a better test case.
Andrew.