X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f X-Recipient: djgpp AT delorie DOT com X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=tYJMwQ5Lkfb7Ie8AZRFrI2YFeeYIa3SnAKU7/a5i4zc=; b=dW8Q/hEYX5uON+SiApQ/qNp0r6DHf/uWfV/4QQddVvqyZg3AxxWK47mxRKj/lenDQA v9rt3WOOFfU1J1V0KFbTF/5L6x2TmKhbsAu/e1EjFSPfVeSmkIHeh8rHgH+EC4Iu70sp kGK48QZB0A1a8CDBgxLjZDNoAGlX7CAhDS60vuaFm/X9E8Te1XFUjhzoKZwa3ipzGFS1 /aMiHFPZwuXp9Sy2W21l8NXk3JWljsIMndniA0s+Y87ztDVFePSxW3SEj+C/3WBGA2Bd bjjC99HbAUbAJZm4g1/ypCA1quuB2Fpi6Jv+IdBkItVJn53CjEPEZto703aD7P9kg20s CKhQ== MIME-Version: 1.0 X-Received: by 10.50.164.138 with SMTP id yq10mr9963387igb.29.1431887540807; Sun, 17 May 2015 11:32:20 -0700 (PDT) In-Reply-To: <5558DBB0.1040504@iki.fi> References: <555889AB DOT 1010608 AT iki DOT fi> <5558DBB0 DOT 1040504 AT iki DOT fi> Date: Sun, 17 May 2015 21:32:20 +0300 Message-ID: Subject: Re: dlopen() crashes when DXE built with with gcc-5.1.0 From: "Ozkan Sezer (sezeroz AT gmail DOT com)" To: djgpp AT delorie DOT com Content-Type: text/plain; charset=UTF-8 Reply-To: djgpp AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk On 5/17/15, Andris Pavenis (andris DOT pavenis AT iki DOT fi) wrote: > On 05/17/2015 04:06 PM, Ozkan Sezer (sezeroz AT gmail DOT com) wrote: >> On 5/17/15, Andris Pavenis (andris DOT pavenis AT iki DOT fi) >> wrote: >>> dlopen() crashes when >>> - DXE is built using gcc-5.1.0 (verified that gcc-4.7.3 is OK, I did not >>> test 4.8 or 4.9 now) >>> - there are unresolved references in DXE >>> >>> tests/dxe/dldemo.c is such example which crashes when DXE is built using >>> gcc-5.1.0. >>> There are no crashes when only dldemo.c and libc is compiled using >>> gcc-5.1, >>> but DXEs with gcc-4.7.3. >>> >>> DXE files without unresolved references seem to work. >>> >>> Andris >> Impossibly remote possibilty, in case your dxe3gen is compiled using an >> x64-hosted gcc5: I just replaced two remaining uses of 'long int' with >> LONG32 (also added compile time checks to coff.h and sys/dxe.h to ensure >> LONG32 is 32 bits). Does it make a difference? (I don't think so, but..) > It would a problem only if I would running dxegen3 under x64 host. dxegen3 > built on > x64 host should not have any problems. > That was the remote possibility I wanted to eliminate, > Rebuilt all under under Windows Vista in DOS session and there were no > improvement > gcc bug or ours?