Date: Thu, 31 Oct 2002 15:51:51 +1030 From: Greg Lewis <glewis@eyesbeyond.com> To: Michael E Mercer <mmercer@nc.rr.com> Cc: Greg Lewis <glewis@eyesbeyond.com>, maruyama@yogotech.com, freebsd-java@FreeBSD.ORG Subject: Re: LimeWire crash gdb information Message-ID: <20021031155151.B35475@misty.eyesbeyond.com> In-Reply-To: <3DC04A50.D8FB8B4D@nc.rr.com>; from mmercer@nc.rr.com on Wed, Oct 30, 2002 at 04:08:32PM -0500 References: <3DBAE791.27A93619@nc.rr.com> <20021027083816.B10962@misty.eyesbeyond.com> <3DBB49F8.941D3E09@nc.rr.com> <3DBB4CEA.E0DC7E1C@nc.rr.com> <3DBB5250.8DA88B27@nc.rr.com> <20021030172314.A31631@misty.eyesbeyond.com> <3DC04A50.D8FB8B4D@nc.rr.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Oct 30, 2002 at 04:08:32PM -0500, Michael E Mercer wrote: > I am no expert in c, but is it possible that the system is reusing a file descriptor before the > jvm code has reset the fd_flags[fd]? > > The LimeWire software is opening and closing sockets left and right very quickly, > so could this be a timing issue with this panic? > > I would really like to help out debugging, so if someone does not mind giving me > a quick tutoring lesson on the code and gdb, I'll jump right in! Well, I think you were right with your initial observation. The internal call to socket() in libc (presumably to send out a query to the nameserver) shouldn't be calling back into the JVM. Whatever else might be going on, this is the root cause. -- Greg Lewis Email : glewis@eyesbeyond.com Eyes Beyond Web : http://www.eyesbeyond.com Information Technology FreeBSD : glewis@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-java" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021031155151.B35475>