Return-Path: Delivered-To: apmail-incubator-harmony-dev-archive@www.apache.org Received: (qmail 41174 invoked from network); 1 Oct 2006 21:38:44 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 1 Oct 2006 21:38:44 -0000 Received: (qmail 10547 invoked by uid 500); 1 Oct 2006 21:38:37 -0000 Delivered-To: apmail-incubator-harmony-dev-archive@incubator.apache.org Received: (qmail 10493 invoked by uid 500); 1 Oct 2006 21:38:37 -0000 Mailing-List: contact harmony-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: harmony-dev@incubator.apache.org Delivered-To: mailing list harmony-dev@incubator.apache.org Received: (qmail 10482 invoked by uid 99); 1 Oct 2006 21:38:37 -0000 Received: from idunn.apache.osuosl.org (HELO idunn.apache.osuosl.org) (140.211.166.84) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 01 Oct 2006 14:38:37 -0700 Authentication-Results: idunn.apache.osuosl.org header.from=weldonwjw@gmail.com; domainkeys=good X-ASF-Spam-Status: No, hits=2.5 required=5.0 tests=DNS_FROM_RFC_ABUSE,HTML_MESSAGE DomainKey-Status: good X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 Received: from [66.249.82.231] ([66.249.82.231:47845] helo=wx-out-0506.google.com) by idunn.apache.osuosl.org (ecelerity 2.1.1.8 r(12930)) with ESMTP id D0/08-05102-A5530254 for ; Sun, 01 Oct 2006 14:38:36 -0700 Received: by wx-out-0506.google.com with SMTP id s13so1542363wxc for ; Sun, 01 Oct 2006 14:38:32 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=kySZI+W9l1V19QUHqwnr+jWMR4UHtEmJOEGzJsvHl94Ghh8gLEZBLIjNx7ofBAaS2qo40Idz7QGqj4FpjlgGOGV/wPK6lrVb3soI8J7NFMTFtR/h4nZg5vgMcMYXu4A33BGlVv1iRvbsitbMWgVJCC8d4OZiRYLra3KyG44OT2M= Received: by 10.90.54.4 with SMTP id c4mr1374430aga; Sun, 01 Oct 2006 14:38:32 -0700 (PDT) Received: by 10.90.79.7 with HTTP; Sun, 1 Oct 2006 14:38:32 -0700 (PDT) Message-ID: <4dd1f3f00610011438q50f6eb1o49eb2d402efc6feb@mail.gmail.com> Date: Sun, 1 Oct 2006 14:38:32 -0700 From: "Weldon Washburn" To: harmony-dev@incubator.apache.org Subject: [classlib][launcher] should we get rid of one of the HyPortLibrary function tables in DRLVM? MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_59235_16666951.1159738712340" X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N ------=_Part_59235_16666951.1159738712340 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline All, Using windows debugger, I see native/launcher/shared/main.c::invocation() receive an incoming argument that looks to be a DRLVM version of HyPortLibrary with all the functions zeroed out. Does anyone else see this?? Passing a HyPortLibrary with the function ptrs nulled out is not the primary concern. At worst, this will cause a sigsegv and should be straight forward to debug. The big concern is accidentally using the classlib/HyPortLibrary function ptr table when DRLVM Threading Manager APIs are intended. This could cause all sorts of strange deadlocks. I have looked at the code to prove or disprove that the two HyPortLibraries are being confused. So far, no luck. There are too many layers to get to the bottom of this quickly. Does anyone know the answer to the above question? If not, should I open a JIRA on this issue? -- Weldon Washburn Intel Middleware Products Division ------=_Part_59235_16666951.1159738712340--