public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: torsten.rueger@firsthop.com
To: gcc-gnats@gcc.gnu.org
Subject: libgcj/2431: static initializers
Date: Fri, 30 Mar 2001 00:26:00 -0000	[thread overview]
Message-ID: <20010330081754.15467.qmail@sourceware.cygnus.com> (raw)

>Number:         2431
>Category:       libgcj
>Synopsis:       static initializers
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Mar 30 00:26:00 PST 2001
>Closed-Date:
>Last-Modified:
>Originator:     torsten.rueger@firsthop.com
>Release:        gcc version 3.0 20010320 (prerelease)
>Organization:
>Environment:
Configured with: ../gcc-20010320/configure --enable-threads=posix --prefix=/tmp/local/ --enable-shared --enable-languages=c++,javaLinux inception 2.2.12-20 #1 Mon Sep 27 10:40:35 EDT 1999 i686 unknown
>Description:
I got some bizzare NullPointer Exception, something like
MyObject o = new MyObject();
o.toString();  // NULL Pointer here
Running from the command I got the nullpointer. Runniing under a debugger I got sigsuspend in the init of the first Thread. So I gave up. 
Just by chance I tried removing a static initializer in MyObject, and the problem disapeared.
I mean I move d
static { someCode}  
into some other init method, and now all works fine
>How-To-Repeat:
I couldn't make a small case for this.
I have 300 classes here, all gnu, that I could send, Makefile and everything included.
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2001-03-30  0:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-30  0:26 torsten.rueger [this message]
2001-09-29 23:38 bryce
2002-01-27 15:58 rodrigc

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=20010330081754.15467.qmail@sourceware.cygnus.com \
    --to=torsten.rueger@firsthop.com \
    --cc=gcc-gnats@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).