public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "artem at bizlink dot ru" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug java/32836]  New: infinite loop (SIGSEGV) in java::lang::Throwable::fillInStackTrace
Date: Fri, 20 Jul 2007 09:53:00 -0000	[thread overview]
Message-ID: <bug-32836-7398@http.gcc.gnu.org/bugzilla/> (raw)

This is Fedora 7.

$ gcj -v
Using built-in specs.
Reading specs from /usr/lib/gcc/i386-redhat-linux/4.1.2/libgcj.spec
rename spec startfile to startfileorig
rename spec lib to liborig
Target: i386-redhat-linux
Configured with: ../configure --prefix=/usr --mandir=/usr/share/man
--infodir=/usr/share/info --enable-shared --enable-threads=posix
--enable-checking=release --with-system-zlib --enable-__cxa_atexit
--disable-libunwind-exceptions
--enable-languages=c,c++,objc,obj-c++,java,fortran,ada --enable-java-awt=gtk
--disable-dssi --enable-plugin
--with-java-home=/usr/lib/jvm/java-1.5.0-gcj-1.5.0.0/jre
--enable-libgcj-multifile --enable-java-maintainer-mode
--with-ecj-jar=/usr/share/java/eclipse-ecj.jar --with-cpu=generic
--host=i386-redhat-linux
Thread model: posix
gcc version 4.1.2 20070502 (Red Hat 4.1.2-12)

There is this curious stack trace (in GDB):

...
#7889 <signal handler called>
#7890 0x006fc7e6 in ?? () from /lib/libgcc_s.so.1
#7891 0x006fd6b2 in _Unwind_Backtrace () from /lib/libgcc_s.so.1
#7892 0x02d9ac4e in _Jv_StackTrace::GetStackTrace () from
/usr/lib/libgcj.so.8rh
#7893 0x02dd5ecc in java::lang::VMThrowable::fillInStackTrace () from
/usr/lib/libgcj.so.8rh
#7894 0x03259492 in java::lang::Throwable::fillInStackTrace () from
/usr/lib/libgcj.so.8rh
#7895 0x03258ddd in java::lang::Throwable::Throwable () from
/usr/lib/libgcj.so.8rh
#7896 0x03258da3 in java::lang::Throwable::Throwable () from
/usr/lib/libgcj.so.8rh
#7897 0x0323cefb in java::lang::Exception::Exception () from
/usr/lib/libgcj.so.8rh
#7898 0x0324369b in java::lang::RuntimeException::RuntimeException () from
/usr/lib/libgcj.so.8rh
#7899 0x032418db in java::lang::NullPointerException::NullPointerException ()
from /usr/lib/libgcj.so.8rh
#7900 0x02d89b08 in ?? () from /usr/lib/libgcj.so.8rh
#7901 <signal handler called>
#7902 0x006fc7e6 in ?? () from /lib/libgcc_s.so.1
#7903 0x006fd6b2 in _Unwind_Backtrace () from /lib/libgcc_s.so.1
---Type <return> to continue, or q <return> to quit---
#7904 0x02d9ac4e in _Jv_StackTrace::GetStackTrace () from
/usr/lib/libgcj.so.8rh
#7905 0x02dd5ecc in java::lang::VMThrowable::fillInStackTrace () from
/usr/lib/libgcj.so.8rh
#7906 0x03259492 in java::lang::Throwable::fillInStackTrace () from
/usr/lib/libgcj.so.8rh
#7907 0x03258ddd in java::lang::Throwable::Throwable () from
/usr/lib/libgcj.so.8rh
#7908 0x03258da3 in java::lang::Throwable::Throwable () from
/usr/lib/libgcj.so.8rh
#7909 0x0323cefb in java::lang::Exception::Exception () from
/usr/lib/libgcj.so.8rh
#7910 0x0324369b in java::lang::RuntimeException::RuntimeException () from
/usr/lib/libgcj.so.8rh
#7911 0x032418db in java::lang::NullPointerException::NullPointerException ()
from /usr/lib/libgcj.so.8rh
#7912 0x02d89b08 in ?? () from /usr/lib/libgcj.so.8rh
#7913 <signal handler called>
#7914 0x006fc7e6 in ?? () from /lib/libgcc_s.so.1
#7915 0x006fd6b2 in _Unwind_Backtrace () from /lib/libgcc_s.so.1
#7916 0x02d9ac4e in _Jv_StackTrace::GetStackTrace () from
/usr/lib/libgcj.so.8rh
#7917 0x02dd5ecc in java::lang::VMThrowable::fillInStackTrace () from
/usr/lib/libgcj.so.8rh
#7918 0x03259492 in java::lang::Throwable::fillInStackTrace () from
/usr/lib/libgcj.so.8rh
#7919 0x03258ddd in java::lang::Throwable::Throwable () from
/usr/lib/libgcj.so.8rh
#7920 0x03258da3 in java::lang::Throwable::Throwable () from
/usr/lib/libgcj.so.8rh
#7921 0x0323cefb in java::lang::Exception::Exception () from
/usr/lib/libgcj.so.8rh
#7922 0x0324369b in java::lang::RuntimeException::RuntimeException () from
/usr/lib/libgcj.so.8rh
#7923 0x032418db in java::lang::NullPointerException::NullPointerException ()
from /usr/lib/libgcj.so.8rh
#7924 0x02d89b08 in ?? () from /usr/lib/libgcj.so.8rh
#7925 <signal handler called>
#7926 0x08368d70 in aga::stpcpy (dest=0x64353f5d "", _src=0x836c92b "&ssi=") at
chomp.cpp:174

As you can see, fillInStackTrace goes into an infinite loop, presumably due to
SIGSEGV in itself, until it stack overflows.

I can provide the binary and the core if somebody is interested in fixing this.


-- 
           Summary: infinite loop (SIGSEGV) in
                    java::lang::Throwable::fillInStackTrace
           Product: gcc
           Version: 4.1.2
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: java
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: artem at bizlink dot ru
 GCC build triplet: i386-redhat-linux
  GCC host triplet: i386-redhat-linux
GCC target triplet: i386-redhat-linux


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


             reply	other threads:[~2007-07-20  9:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-20  9:53 artem at bizlink dot ru [this message]
2007-07-20 10:01 ` [Bug java/32836] " artem at bizlink dot ru
2007-07-20 10:38 ` artem at bizlink dot ru
2007-07-20 11:28 ` artem at bizlink dot ru
2007-07-20 11:34 ` artem at bizlink dot ru
2007-07-20 11:39 ` artem at bizlink dot ru
2007-07-20 14:53 ` [Bug libgcj/32836] " pinskia at gcc dot gnu dot org
2007-07-24 14:34 ` tromey 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=bug-32836-7398@http.gcc.gnu.org/bugzilla/ \
    --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).