Date: Tue, 26 Feb 2002 11:04:32 -0800 From: Bill Huey <billh@gnuppy.monkey.org> To: "Koster, K.J." <K.J.Koster@kpn.com> Cc: "FreeBSD Java mailing list (E-mail)" <freebsd-java@freebsd.org> Subject: Re: 1.3.1p6 dies sigbus with threads Message-ID: <20020226190432.GA2002@gnuppy.monkey.org> In-Reply-To: <20020226185727.GA1920@gnuppy.monkey.org> References: <59063B5B4D98D311BC0D0001FA7E452205FDA3A4@l04.research.kpn.com> <20020226185727.GA1920@gnuppy.monkey.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Feb 26, 2002 at 10:57:27AM -0800, Bill Huey wrote: > What I do is attach GDB with symbol references to an already running JVM > process and then work things from there. Move into the directory and invoke > gdb to get the symbols or something like that. I'm not sure how this is > going to help you out though. To clarify... I mean you'll have to manipulate the gdb paths a bit to get it to load up the .so symbols. I don't remember exactly how I did it. Hmmm... Oh, there's a directory that's symbolically linked to bin/, so move into that area, "gdb java" or something like that and i'll load up the symbols. I don't think this is going to help out though. Also, there's a means of flipping on the C based bytecode interpreter instead of the assembler optimized one. That should give you more concrete checks. It was also the means that I found out where the SEGV was for that wierd waiting-queue wackiness I ran into at the end of last year. That should be a command line switch (I can't rememeber off hand) or you can just look at the JVM initialization code and hand glue it it. Go for the command line option if you know what it is. That's all I can help you with for now. bill 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?20020226190432.GA2002>