This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: SIGABRT?
> > Program received signal SIGABRT, Aborted.
> > 0x0825fae5 in __getdents ()
> Well its crashing inside glibc. Check that the arguments being passed to
> readdir_r are correct?
Okay, um, is there an easy way to do this? I'm not too skilled with
gdb. Or do I have to insert printf()'s into libgcj and recompile?
Also, this might not be specific to java::io::File::performList -- by
passing different arguments to my program, I can get it to SIGABRT in
various places. Here's another example:
Program received signal SIGABRT, Aborted.
0x08261a04 in __libc_read ()
Current language: auto; currently c++
(gdb) bt
#0 0x08261a04 in __libc_read ()
#1 0x00001000 in ?? ()
#2 0x081fb985 in java::io::FileDescriptor::read(JArray<char>*, int, int) (this=0x1000, buffer=0x8732008, offset=4096, count=141762568)
at java/io/natFileDescriptor.cc:261
Does this mean that there's some larger cause at work? Do SIGABRTs
result from MMU exceptions (I thought that was SEGV), or do they only
happen when the program explicitly asks for one (via abort())?
Thanks for the help.
- a
--
Sick of HTML user interfaces?
www.xwt.org