public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Jeff Dahl - Test/MTI <jddahl@micron.com>
To: tromey@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org
Subject: Re: java/1376
Date: Mon, 25 Jun 2001 14:06:00 -0000	[thread overview]
Message-ID: <20010625210600.20574.qmail@sourceware.cygnus.com> (raw)

The following reply was made to PR java/1376; it has been noted by GNATS.

From: Jeff Dahl - Test/MTI <jddahl@micron.com>
To: gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org, tromey@gcc.gnu.org,
        gcc-bugs@gcc.gnu.org, java-prs@gcc.gnu.org, jthwaites@michaelhouse.com
Cc:  
Subject: Re: java/1376
Date: Mon, 25 Jun 2001 14:59:42 -0600

 I also encountered this problem on gcc 3.0.  I've "continued", but am not sure
 
 what I'm looking for.  Thanks,
 
 Jeff
 
 >uname -a
 
 SunOS 5.6 Generic_105181-25 sun4m sparc SUNW,SPARCstation-20
 
 >gdb jsums
 GNU gdb 4.18
 Copyright 1998 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 "sparc-sun-solaris2.5.1"...
 (gdb) run
 Starting program: /amd/tesfs1/tesfs1dg/u12/jddahl/java/jsums
 [New LWP    2        ]
 [New LWP    3        ]
 
 Program received signal SIGSEGV, Segmentation fault.
 0xef361df8 in GC_find_limit (p=0xefffe894 "", up=1)
     at ../../../gcc/boehm-gc/os_dep.c:644
 644                     GC_noop1((word)(*result));
 (gdb) cont
 Continuing.
 [New LWP    4        ]
 
 Program received signal SIGLWP, Signal LWP.
 0xef7c5960 in ?? ()
 (gdb) cont
 Continuing.
 [New LWP    5        ]
 [New Thread 5 (LWP 3)]
 [Switching to Thread 5 (LWP 3)]
 
 Program received signal SIGSEGV, Segmentation fault.
 0xef5e832c in _ZN4java3sql13DriverManager10getDriversEv ()
     at ../../../gcc/libjava/java/sql/DriverManager.java:267
 267           if (!obj.getClass().getClassLoader().equals(cl))
 Current language:  auto; currently java
 (gdb) cont
 Continuing.
 
 Program received signal SIGSEGV, Segmentation fault.
 _Z20_Jv_IsAssignableFromPN4java4lang5ClassES2_ (target=0x0, source=0x1e2ce0)
     at ../../../gcc/libjava/java/lang/Class.h:174
 174         {
 Current language:  auto; currently c++
 (gdb) cont
 Continuing.
 
 Program received signal SIGSEGV, Segmentation fault.
 _Z20_Jv_IsAssignableFromPN4java4lang5ClassES2_ (target=0x0, source=0x1e2ce0)
     at ../../../gcc/libjava/java/lang/Class.h:174
 174         {
 (gdb)
 
 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=1376&database=gcc
 
 
 


             reply	other threads:[~2001-06-25 14:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-25 14:06 Jeff Dahl - Test/MTI [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-06-26  9:46 java/1376 Tom Tromey
2001-06-25 15:26 java/1376 Jeff Sturm
2001-04-01  0:00 java/1376 bryce

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=20010625210600.20574.qmail@sourceware.cygnus.com \
    --to=jddahl@micron.com \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=tromey@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).