[Bug target/23621] New: gcj-dbtool aborts on m68k-linux

[Bug target/23621] New: gcj-dbtool aborts on m68k-linux

[debian-gcc at lists dot debian dot org]

[forwarded from http://bugs.debian.org/312830]

4.0.2 20050821, binutils-2.16.1, glibc-2.3.5 (crest/unstable).

On Sat, Jun 11, 2005 at 01:15:30AM +0200, Christian T. Steigies wrote:
> 
> Running it from gdb now, it seems to take a LOT longer...

Starting program: /usr/bin/gcj-dbtool-4.0 -n /var/lib/gcj-4.0/classmap.db
[Thread debugging using libthread_db enabled]
[New Thread 16384 (LWP 4569)]
[New Thread 32769 (LWP 4591)]
[New Thread 16386 (LWP 4592)]
Exception during runtime initialization

Program received signal SIGABRT, Aborted.
[Switching to Thread 16384 (LWP 4569)]
0xc1095c1e in kill () from /lib/libc.so.6
(gdb) bt
#0  0xc1095c1e in kill () from /lib/libc.so.6
#1  0xc0ffed34 in pthread_kill () from /lib/libpthread.so.0
#2  0xc0ffefae in raise () from /lib/libpthread.so.0
#3  0xc1095a9a in raise () from /lib/libc.so.6
#4  0xc1096a46 in abort () from /lib/libc.so.6
#5  0xc0715fc2 in _Jv_Throw (value=0xc122cf00) at
../../../src/libjava/exception.cc:113
#6  0xc074b0d6 in java.lang.VMClassLoader.transformException(java.lang.Class,
java.lang.Throwable) (clazz=0xc0c29308,
    x=0xc122cf00) at ../../../src/libjava/java/lang/VMClassLoader.java:131
#7  0xc072b174 in java::lang::VMClassLoader::resolveClass (klass=0xc0c29308)
    at ../../../src/libjava/java/lang/natVMClassLoader.cc:49
#8  0xc072490c in java::lang::Class::initializeClass (this=0xc0c29308) at
../../../src/libjava/java/lang/natClass.cc:728
#9  0xc070b50e in _Jv_AllocObjectNoFinalizer (klass=0xc0c29308) at Class.h:579
#10 0xc09eb58c in java.lang.ConcreteProcess$ProcessManager.finit$()
(this=0xc11ad900) at java/lang/ConcreteProcess.java:42
#11 0xc09eb5f8 in
java.lang.ConcreteProcess$ProcessManager.ConcreteProcess$ProcessManager()
(this=0xc11ad900)
    at java/lang/ConcreteProcess.java:35
#12 0xc09ebf9c in java.lang.ConcreteProcess.ConcreteProcess(java.lang.String[],
java.lang.String[], java.io.File) (
    this=0xc11ad940, progarray=0xc1226078, envp=0x0, dir=0x0) at
java/lang/ConcreteProcess.java:376
#13 0xc072709e in java::lang::Runtime::execInternal (this=0xc11c1bd0,
cmd=0xc1226078, env=0x0, dir=0x0)
    at ../../../src/libjava/java/lang/natRuntime.cc:644
#14 0xc073f64c in java.lang.Runtime.exec(java.lang.String[], java.lang.String[],
java.io.File) (this=0xc11c1bd0,
    cmd=0xc1226078, env=0x0, dir=0x0) at
../../../src/libjava/java/lang/Runtime.java:539
#15 0xc073f5b4 in java.lang.Runtime.exec(java.lang.String[]) (this=0xc11c1bd0,
cmd=0xc1226078)
    at ../../../src/libjava/java/lang/Runtime.java:491
#16 0xc07a599e in gnu.gcj.runtime.NameFinder.NameFinder() (this=0xc122beb0)
    at ../../../src/libjava/gnu/gcj/runtime/NameFinder.java:131
#17 0xc074c2ec in java.lang.VMThrowable.getStackTrace(java.lang.Throwable)
(this=0xc1225bb0, t=0xc122cf90)
    at ../../../src/libjava/java/lang/VMThrowable.java:98
#18 0xc074ad20 in java.lang.Throwable.getStackTrace() (this=0xc122cf90)
    at ../../../src/libjava/java/lang/Throwable.java:526
#19 0xc074aae0 in java.lang.Throwable.stackTraceString() (this=0xc122cf90)
    at ../../../src/libjava/java/lang/Throwable.java:421
#20 0xc074acac in java.lang.Throwable.printStackTrace(java.io.PrintStream)
(this=0xc122cf90, s=0xc11c2920)
    at ../../../src/libjava/java/lang/Throwable.java:361
#21 0xc074a92c in java.lang.Throwable.printStackTrace() (this=0xc122cf90)
    at ../../../src/libjava/java/lang/Throwable.java:350
#22 0xc070c50a in _Jv_RunMain (vm_args=0x0, klass=0x800073ce, name=0x0, argc=3,
argv=0xeffff8a4, is_jar=Variable "is_jar" is not available.
)
    at ../../../src/libjava/prims.cc:1345
#23 0xc070c58e in _Jv_RunMain (klass=0x800073ce, name=0x0, argc=3,
argv=0xeffff8a4, is_jar=The value of variable 'is_jar' is distributed across several
locations, and GDB cannot access its value.

)
    at ../../../src/libjava/prims.cc:1364
#24 0xc070c5b0 in JvRunMain (klass=0x800073ce, argc=3, argv=0xeffff8a4) at
../../../src/libjava/prims.cc:1370
#25 0x800025fa in ?? ()
#26 0x800073ce in data_start ()
#27 0x00000003 in ?? ()
#28 0xeffff8a4 in ?? ()
#29 0xeffff880 in ?? ()
#30 0xc1086f18 in __libc_start_main () from /lib/libc.so.6
#31 0xc1086f18 in __libc_start_main () from /lib/libc.so.6
#32 0x80002542 in ?? ()

-- 
           Summary: gcj-dbtool aborts on m68k-linux
           Product: gcc
           Version: 4.1.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: target
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: debian-gcc at lists dot debian dot org
                CC: gcc-bugs at gcc dot gnu dot org,schwab at suse dot de
GCC target triplet: m68k-linux


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

[Bug target/23621] gcj-dbtool aborts on m68k-linux

[pinskia at gcc dot gnu dot org]

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |EH


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

[Bug target/23621] gcj-dbtool aborts on m68k-linux

[pinskia at gcc dot gnu dot org]

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |wrong-code


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

[Bug target/23621] gcj-dbtool aborts on m68k-linux

[schwab@linux-m68k.org]

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

Andreas Schwab <schwab@linux-m68k.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
      Known to work|                            |4.4.0
         Resolution|                            |FIXED

--- Comment #2 from Andreas Schwab <schwab@linux-m68k.org> 2011-07-30 08:45:41 UTC ---
Assuming fixed.

[Bug target/23621] gcj-dbtool aborts on m68k-linux

[tg at mirbsd dot org]

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

Thorsten Glaser <tg at mirbsd dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tg at mirbsd dot org

--- Comment #1 from Thorsten Glaser <tg at mirbsd dot org> 2011-01-04 05:44:10 UTC ---
The Debian bug has been closed. Seeing that I got strange messages
during package building…

Setting up ecj (3.5.1-1) ...
Setting up libecj-java-gcj (3.5.1-1) ...
gcj-dbtool-4.4 succeeded unexpectedly
Setting up ecj-gcj (3.5.1-1) ...

… and that running “gcj-dbtool-4.4 -n /tmp/foo.db” succeeds, this
can probably be closed. HTH, HAND.