public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "debian-gcc at lists dot debian dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/23602] [4.1 regression] 1081 test failures in libjava, when configured for i486-linux
Date: Fri, 02 Sep 2005 22:21:00 -0000	[thread overview]
Message-ID: <20050902222107.31357.qmail@sourceware.org> (raw)
In-Reply-To: <20050828164012.23602.debian-gcc@lists.debian.org>


------- Additional Comments From debian-gcc at lists dot debian dot org  2005-09-02 22:21 -------
(In reply to comment #9)
> About comment #7 - it would be helpful to know how the execution tests
> fail.  For instance a gdb backtrace from one of them.

it would, but running them from the commandline let's the test succeed :-/

Running the ArrayStore test from 20050715, I get

$ gdb ./ArrayStore.exe
GNU gdb 6.3-debian
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu"...Using host libthread_db library
"/lib/libthread_db.so.1".

(gdb) run
Starting program:
/home/packages/gcc/cvs/build-20050715-12/i486-linux-gnu/libjava/testsuite/ArrayStore.exe
[Thread debugging using libthread_db enabled]
[New Thread 1450720736 (LWP 14599)]
[New Thread 1459313584 (LWP 14604)]
java.lang.ArrayStoreException
java.lang.ArrayStoreException

Program received signal SIGABRT, Aborted.
[Switching to Thread 1450720736 (LWP 14599)]
0x5668362b in raise () from /lib32/tls/libc.so.6
(gdb) bt
#0  0x5668362b in raise () from /lib32/tls/libc.so.6
#1  0x56684d3f in abort () from /lib32/tls/libc.so.6
#2  0x55bd0451 in _Jv_Throw (value=0xffffd3ac)
    at ../../../gcc-20050715-12/libjava/exception.cc:111
#3  0x55bc4bd0 in _Jv_ThrowBadArrayIndex (bad_index=1)
    at ../../../gcc-20050715-12/libjava/prims.cc:353
#4  0x080491a8 in ArrayStore.b(java.lang.String[]) (this=0x47f00, sa=Variable
"sa" is not available.
)
    at Throwable.java:50
#5  0x00000001 in ?? ()
#6  0x08049120 in ArrayStore::a () at Throwable.java:45
#7  0x00047f00 in ?? ()
#8  0x08048f2f in ArrayStore.main(java.lang.String[]) (args=0x563a7e88)
    at ArrayStore.java:30
#9  0x55befd0b in gnu::java::lang::MainThread::call_main (this=0x61f18)
    at ../../../gcc-20050715-12/libjava/gnu/java/lang/natMainThread.cc:47
#10 0x55c29e66 in gnu.java.lang.MainThread.run() (this=0x61f18)
    at MainThread.java:105
#11 0x55bfea26 in _Jv_ThreadRun (thread=0x61f18)
    at ../../../gcc-20050715-12/libjava/java/lang/natThread.cc:296
#12 0x55bc5ba5 in _Jv_RunMain (vm_args=0x0, klass=0x804a980, name=0x0, argc=1,
    argv=0xffffd734, is_jar=false)
    at ../../../gcc-20050715-12/libjava/prims.cc:1386
#13 0x55bc5cf0 in _Jv_RunMain (klass=0x804a980, name=0x0, argc=1,
    argv=0xffffd734, is_jar=false)
    at ../../../gcc-20050715-12/libjava/prims.cc:1397
#14 0x55bc5d28 in JvRunMain (klass=0x804a980, argc=1, argv=0xffffd734)
    at ../../../gcc-20050715-12/libjava/prims.cc:1403
#15 0x08048ea8 in main (argc=1, argv=0xffffd734) at /tmp/cc7ZPyq6.i:11

Running the same test with 20050717, the debugger hangs:
$ gdb ./ArrayStore.exe
GNU gdb 6.3-debian
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-linux"...Using host libthread_db library
"/lib/tls/libthread_db.so.1".

(gdb) run
Starting program:
/home/packages/gcc/cvs/build-20050717/i486-linux-gnu/libjava/testsuite/ArrayStore.exe
[Thread debugging using libthread_db enabled]
Error while reading shared library symbols:
Cannot find new threads: generic error



-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23602


  parent reply	other threads:[~2005-09-02 22:21 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-28 16:41 [Bug target/23602] New: " debian-gcc at lists dot debian dot org
2005-08-28 17:20 ` [Bug target/23602] " debian-gcc at lists dot debian dot org
2005-08-28 21:58 ` pinskia at gcc dot gnu dot org
2005-08-29 21:08 ` debian-gcc at lists dot debian dot org
2005-08-30  2:46 ` rth at gcc dot gnu dot org
2005-08-30  6:00 ` rth at gcc dot gnu dot org
2005-08-30  7:33 ` debian-gcc at lists dot debian dot org
2005-08-31 10:17 ` debian-gcc at lists dot debian dot org
2005-08-31 14:12 ` debian-gcc at lists dot debian dot org
2005-09-02 21:39 ` rth at gcc dot gnu dot org
2005-09-02 21:46 ` tromey at gcc dot gnu dot org
2005-09-02 22:09 ` rth at gcc dot gnu dot org
2005-09-02 22:21 ` debian-gcc at lists dot debian dot org [this message]
2005-09-05 13:26 ` debian-gcc at lists dot debian dot org
2005-09-26 13:23 ` debian-gcc at lists dot debian dot org
     [not found] <bug-23602-5724@http.gcc.gnu.org/bugzilla/>
2005-10-05 18:19 ` cvs-commit at gcc dot gnu dot org
2005-10-05 18:23 ` rth at gcc dot gnu dot org
2006-01-21  2:11 ` aoliva at gcc dot gnu dot org
2006-03-17  6:25 ` aoliva at gcc dot gnu dot org

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=20050902222107.31357.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).