public inbox for rhug-rhats@sourceware.org
 help / color / mirror / Atom feed
From: Gary Benson <gbenson@redhat.com>
To: rhug-rhats@sources.redhat.com
Subject: Re: segfault when running ant
Date: Fri, 28 Nov 2003 12:04:00 -0000	[thread overview]
Message-ID: <20031128120435.GA12877@redhat.com> (raw)
In-Reply-To: <1070019719.27083.86.camel@ua-213-114-26-86.cust.bredbandsbolaget.se>

Noa Resare wrote:
> Starting program: /usr/bin/ant
> [Thread debugging using libthread_db enabled]
> [New Thread -1084473216 (LWP 4823)]
>  
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread -1084473216 (LWP 4823)]
> 0x00751ada in
> org.apache.xerces.impl.xs.XSDDescription.equals(java.lang.Object)
>     (this=@6811c02, descObj=@bf37d8a0)
>     at upstream/src/org/apache/xerces/impl/xs/XSDDescription.java:226
> 226         public boolean equals(Object descObj) {
> Current language:  auto; currently java
> 
> How should I go about debugging this?

The way I debug things is to keep a copy of gcc and RHUG built with
-O0, etc, and try and reproduce the failure in that.  That way I can
change things easily.

Can you generate a backtrace for the above?  Also, are you using the
very latest Naoko packages?  Including Naoko gcc-ssa?  The gcc-ssa in
Fedora will not work.

> ps. I have no previous experience using gcj, so segfaults from java
> code is a new thing to me.

Debugging them is pretty much like debugging C or C++, except that
listings come up in Java ;)

Gary

  reply	other threads:[~2003-11-28 12:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-28 11:42 Noa Resare
2003-11-28 12:04 ` Gary Benson [this message]
2003-11-28 12:28   ` Noa Resare
2003-11-28 13:43     ` Gary Benson
2003-11-28 18:17     ` Jeff Sturm
2003-11-28 22:35 ` Noa Resare
2003-12-16 10:36 ` Noa Resare

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=20031128120435.GA12877@redhat.com \
    --to=gbenson@redhat.com \
    --cc=rhug-rhats@sources.redhat.com \
    /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).