This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: debugging threads vs processes
- To: Jeff Sturm <jsturm at one-point dot com>
- Subject: Re: debugging threads vs processes
- From: Tom Tromey <tromey at redhat dot com>
- Date: 13 Jul 2001 09:45:36 -0600
- Cc: Per Bothner <per at bothner dot com>, java-discuss at sources dot redhat dot com
- References: <Pine.LNX.4.10.10107130148140.3005-100000@mars.deadcafe.org>
- Reply-To: tromey at redhat dot com
>>>>> "Jeff" == Jeff Sturm <jsturm@one-point.com> writes:
Per> Thanks to everybody who responded! I still have no idea why the
Per> server is crashing (possibly some weird interaction between
Per> Apache's use of threads and Java's use of threads?), but my
Per> confusion is now at a higher plane of enlightenment!
Jeff> Hmm... are you loading libgcj.so dynamically? The GC may not
Jeff> track threads properly unless it is loaded at startup.
It might be worse than that. boehm-gc overrides various pthread_*
functions so that it can keep track of what is going on. Apache might
need to be recompiled so that it calls these functions. At least, if
Apache uses threads and if it can create new threads that use libgcj
without notifying the GC. This is all platform dependent. Offhand I
don't know which platforms use overrides and which use other methods.
Tom