public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "rickard dot narstrom at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug java/19586] gij exits with SIGABR
Date: Sun, 23 Jan 2005 20:15:00 -0000	[thread overview]
Message-ID: <20050123201543.29167.qmail@sourceware.org> (raw)
In-Reply-To: <20050123105033.19586.rickard.narstrom@gmail.com>


------- Additional Comments From rickard dot narstrom at gmail dot com  2005-01-23 20:15 -------
(In reply to comment #4)
> (In reply to comment #3)
> > the segfault seemed to be a tempurary failure its back to abort now
> 
> Now it sounds like your machine has bad memory.  Can you check your memory?

I don't think so it probebly some bad updated env-vars that were back to correct
values after a re-login or something like that.

But if it is my memory how do I test it? Is it a program I can use?

-- 


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


  parent reply	other threads:[~2005-01-23 20:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-23 10:50 [Bug java/19586] New: " rickard dot narstrom at gmail dot com
2005-01-23 15:50 ` [Bug java/19586] " pinskia at gcc dot gnu dot org
2005-01-23 17:59 ` rickard dot narstrom at gmail dot com
2005-01-23 19:52 ` rickard dot narstrom at gmail dot com
2005-01-23 19:54 ` pinskia at gcc dot gnu dot org
2005-01-23 20:15 ` rickard dot narstrom at gmail dot com [this message]
2005-01-27 12:49 ` rmathew at gcc dot gnu dot org
2005-01-27 17:39 ` rickard dot narstrom at gmail dot com
2005-01-27 20:56 ` mark at klomp dot org
2005-01-27 22:18 ` rickard dot narstrom at gmail dot com
2005-01-27 22:29 ` rickard dot narstrom at gmail dot com
2005-01-27 22:44 ` mark at klomp dot org
2005-07-31  4:16 ` pinskia 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=20050123201543.29167.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=java-prs@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).