Segfault in org::w3c::dom::Node::class

Tue Oct 11 17:52:00 GMT 2005

Andrew Haley writes:
 > Khiraly writes:
 > > 2005年10月06日, cs keltezÃ©ssel 08:44-kor David Daney ezt Ãrta:
 > > > SIGSEGV is usually a "normal" occurrence in the gcj runtime. On most 
 > > > platforms it is converted into a NullPointerException and then handled 
 > > > by the exception handling framework.
 > > > 
 > > > You should try to determine if this is just a normal instance of 
 > > > NullPointerException or if something went wrong (i.e. is the faulting 
 > > > address close to 0 which is a normal NPE). You program is aborting 
 > > > which could indicate a problem encountered by the exception processing 
 > > > code in libgcj. This type of problem is exceptionally fun to debug (no 
 > > > pun intended).
 > > 
 > > I have written a small test program to demonstrate the problem. 
 > > 
 > > Now Im quite sure that this is a bug with gcj and not with my program.
 > > 
 > > I can compile with javac, but segfault with gcj.
 > > 
 > > khiraly@elite:~/saxsux$ javac SaxSux.java
 > > khiraly@elite:~/saxsux$ java SaxSux config.xml
 > > Teszt
 > > true
 > > khiraly@elite:~/saxsux$ gcj-4.0 --main=SaxSux SaxSux.java
 > > khiraly@elite:~/saxsux$ ./a.out config.xml
 > > Aborted
 > > khiraly@elite:~/saxsux$
 > > 
 > > 
 > > Here is the two file to demonstrate the problem:
 > > http://khiraly.4242.hu/tmp/saxsux/SaxSux.java
 > > http://khiraly.4242.hu/tmp/saxsux/config.xml
 > > 
 > > Can somebody verify this problem please?
 > 
 > Yes. It's some sort of problem with interface dispatch when calling
 > from non-BC code. I'm working on it, and I'll have an answer later
 > today.
OK, I found the bug and I'm working on a patch.
Khiraly, could you please go to http://gcc.gnu.org/bugzilla/ and
create a gcc bug report for this? The "Component" should be java.
Drop me an email if you do this.
Thanks,
Andrew.