public inbox for java@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andrew Haley <aph@redhat.com>
To: Matthias Klose <doko@ubuntu.com>
Cc: java@gcc.gnu.org
Subject: libgcj testsuite FAILs on Ubuntu
Date: Wed, 05 Aug 2009 10:58:00 -0000	[thread overview]
Message-ID: <4A7965CE.7080601@redhat.com> (raw)

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

A simple test reveals that dladdr() doesn't work:

#define _GNU_SOURCE
#include <stdio.h>
#include <dlfcn.h>

void dosym(const char *s, void *p)
{
  Dl_info addr_info;
  int success = dladdr (p, &addr_info);

  if (success)
    {
      fprintf (stdout, "%s=%p\n", s, p);
      fprintf (stdout, "%s is at %p,\n",
	       addr_info.dli_sname, addr_info.dli_fbase);
    }
}

void main()
{
  dosym ("printf", (void*)printf);
  dosym ("open", (void*)fopen);
}

aph@babbage-aph:~$ gcc test_dladdr.c -g -ldl
aph@babbage-aph:~$ ./a.out
printf=0x83f0
printf is at 0x8000,
open=0x83e4
fopen is at 0x8000,

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.

Andrew.

             reply	other threads:[~2009-08-05 10:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-05 10:58 Andrew Haley [this message]
2009-08-05 11:08 ` Matthias Klose
2009-08-05 11:12   ` Andrew Haley
2009-08-05 13:07     ` Andrew Haley
2009-08-05 13:50       ` Andrew Haley

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4A7965CE.7080601@redhat.com \
    --to=aph@redhat.com \
    --cc=doko@ubuntu.com \
    --cc=java@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).