Date: Tue, 18 Oct 2005 00:04:22 EST-10EDT,10,-1,0,7200,3,-1,0,7200,3600 Subject: [UnixOS2_Archive] No. 634 ************************************************** Monday 17 October 2005 Number 634 ************************************************** Subjects for today 1 Re: OpenSSL v0.9.8 : John Poltorak 2 Re: LIBC Error: Couldn't register process in shared memory! : mikus at bga.com (Mikus Grinbergs) 3 Re: OpenSSL v0.9.8 : Stefan.Neis at t-online.de 4 Re: LIBC Error: Couldn't register process in shared memory! : Knut St. Osmundsen" 5 Re: LIBC Error: Couldn't register process in shared memory! : Dave Yeo" 6 Re: LIBC Error: Couldn't register process in shared memory! : IanM" 7 Re: OpenSSL v0.9.8 : John Poltorak 8 GNU Patch v2.54 : John Poltorak 1 gdb for gcc 3.3.2 and 3.3.5? : Jon Saxton **= Email 1 ==========================** Date: Sun, 16 Oct 2005 19:18:54 +0100 From: John Poltorak Subject: Re: OpenSSL v0.9.8 On Fri, Oct 14, 2005 at 11:13:59PM +0200, Stefan.Neis at t-online.de wrote: > Hi, > > > > Has anyone tried building OpenSSL v0.9.8? Any success? > > > > I built it with EMX -- I used it to build Pine 4.64. > > > > There were a few changes I had to make but I don't > > remember what they were > > off-hand and I won't have a chance to look it up until > > the weekend. > > IIRC, there was a problem found in one of the later 0.9.7 releases > and there was a patch submitted for it which for some reason doesn't > seem to have made it into OpenSSL's CVS. I googled for OpenSSL > and OS2 and found a patch for 0.9.7d (or later, don't really remember > right now) that both applied cleanly and made OpenSSL-0.9.8 compile. I have the following patched which worked fine for v0.9.7e but doesn't work for v0.9.8 *** openssl-0.9.7e/crypto/o_str.c~ Thu Jul 8 08:32:52 2004 --- openssl-0.9.7e/crypto/o_str.c Sun Jan 9 22:13:10 2005 *************** *** 89,92 **** --- 89,94 ---- #elif defined(OPENSSL_SYS_WINDOWS) return _strnicmp(str1, str2, n); + #elif defined(OPENSSL_SYS_OS2) + return strnicmp(str1, str2, n); #else return strncasecmp(str1, str2, n); *************** *** 99,102 **** --- 101,106 ---- #elif defined(OPENSSL_SYS_WINDOWS) return _stricmp(str1, str2); + #elif defined(OPENSSL_SYS_OS2) + return stricmp(str1, str2); #else return strcasecmp(str1, str2); Is this the patch you are referring to or something else? > HTH, > Stefan -- John **= Email 2 ==========================** Date: Sun, 16 Oct 2005 14:09:04 -0500 From: mikus at bga.com (Mikus Grinbergs) Subject: Re: LIBC Error: Couldn't register process in shared memory! On Sun, 16 Oct 2005 13:20:36 +0400 Roman Trunov wrote: > > Please forgot the mail about source code which I've sent to you > directly. I've just found it with help of debugger, disassember and some > luck. Yes, very stupid bug. > > I've patched ONE BYTE in the existing dll, changing mov to lea: > > libc06r1.dll (912103 bytes) > OFFSET 000173E7: 8B => 8D > > And it's working well now... Are you sure? On my libc06r1, the '8B' byte appears to be at offset 000173E5 mikus **= Email 3 ==========================** Date: Sun, 16 Oct 2005 22:50:03 +0100 From: Stefan.Neis at t-online.de Subject: Re: OpenSSL v0.9.8 Hi, > I have the following patched which worked fine for v0.9.7e but doesn't > work for v0.9.8 (patch about stricmp vs. strcasecmp snipped) > Is this the patch you are referring to or something else? Close, but not quite. That part seems to have made it to the CVS, what I've been thinking of was the patch to util/pl/OS2-EMX.pl given in http://www.mail-archive.com/openssl-dev at openssl.org/msg18635.html, IIRC. That seems to not have been applied for some reason... HTH, Stefan **= Email 4 ==========================** Date: Sun, 16 Oct 2005 23:04:25 +0200 From: "Knut St. Osmundsen" Subject: Re: LIBC Error: Couldn't register process in shared memory! I knew it was a stupid bug. Thanks for finding it. Next build will work on Warp4 Knut St. Osmundsen wrote: > >> It's a simple and probably very stupid bug, in LIBC. > > > Please forgot the mail about source code which I've sent to you > directly. I've just found it with help of debugger, disassember and some > luck. Yes, very stupid bug. > > On second attempt to allocate shared memory, you've typed: > > DosAllocSharedMem( ....., address); > > while it must be > > DosAllocSharedMem( ....., &address); > > I wonder why it wasn't diagnosed by warnings. > > I've patched ONE BYTE in the existing dll, changing mov to lea: > > libc06r1.dll (912103 bytes) > OFFSET 000173E7: 8B => 8D > > And it's working well now... > > Roman > > **= Email 5 ==========================** Date: Sun, 16 Oct 2005 14:45:54 -0700 (PDT) From: "Dave Yeo" Subject: Re: LIBC Error: Couldn't register process in shared memory! On Sun, 16 Oct 2005 14:09:04 -0500, Mikus Grinbergs wrote: >> I've patched ONE BYTE in the existing dll, changing mov to lea: >> >> libc06r1.dll (912103 bytes) >> OFFSET 000173E7: 8B => 8D >> >> And it's working well now... > >Are you sure? > >On my libc06r1, the '8B' byte appears to be at offset 000173E5 Here it is also at 000173E7, seems you've lost 2 bytes Dave **= Email 6 ==========================** Date: Mon, 17 Oct 2005 12:20:07 +1000 (EST) From: "IanM" Subject: Re: LIBC Error: Couldn't register process in shared memory! This maybe the reason I've got a problem with Yuri's last CLAMAV build. brings the server down anywere from 5 mins to 2 hours, just glad it's set for reboot on error, though I've never been able to find out why so I had to go back to clamav-0.86-os2.zip, seems to only happen when I setup the demon for weasel to use when scanning incoming emails for virus's - which would explain it :) On Sun, 16 Oct 2005 13:20:36 +0400, Roman Trunov wrote: > Knut St. Osmundsen wrote: > > > It's a simple and probably very stupid bug, in LIBC. > > Please forgot the mail about source code which I've sent to you > directly. I've just found it with help of debugger, disassember and some > luck. Yes, very stupid bug. > > On second attempt to allocate shared memory, you've typed: > > DosAllocSharedMem( ....., address); > > while it must be > > DosAllocSharedMem( ....., &address); > > I wonder why it wasn't diagnosed by warnings. > > I've patched ONE BYTE in the existing dll, changing mov to lea: > > libc06r1.dll (912103 bytes) > OFFSET 000173E7: 8B => 8D > > And it's working well now... > > Roman > Cheers IanM http://www.os2site.com/ Elvis, Pharoah, and MS-BOB: Which one is still alive? **= Email 7 ==========================** Date: Mon, 17 Oct 2005 11:40:18 +0100 From: John Poltorak Subject: Re: OpenSSL v0.9.8 On Sun, Oct 16, 2005 at 10:50:03PM +0100, Stefan.Neis at t-online.de wrote: > Hi, > > > I have the following patched which worked fine for v0.9.7e but doesn't > > work for v0.9.8 > > (patch about stricmp vs. strcasecmp snipped) > > > Is this the patch you are referring to or something else? > > Close, but not quite. That part seems to have made it to the CVS, what I've > been thinking of was the patch to util/pl/OS2-EMX.pl given in > http://www.mail-archive.com/openssl-dev at openssl.org/msg18635.html, IIRC. Did you apply that patch exactly as it appears? I got Hunk #1 FAILED at 68. but can't see any obvious reason why it should have failed. > HTH, > Stefan -- John **= Email 8 ==========================** Date: Mon, 17 Oct 2005 13:51:44 +0100 From: John Poltorak Subject: GNU Patch v2.54 Has anyone managed to build GNU Patch v2.54? I know it has been ported by Jun SAWATAISHI but I've never managed to build it. I'd like to know if anyone has had any success with it and maybe point out what I'm doing wrong. -- John **= Email 1 ==========================** Date: Mon, 17 Oct 2005 08:46:03 -0400 From: Jon Saxton Subject: gdb for gcc 3.3.2 and 3.3.5? The gdb that works for gcc 3.2.1 emx does not recognise my executables compiled with Innotek gcc 3.2.2 and as far as I know there has been no update of gdb since the one that came with gcc 2.8.1. Which of course leads to the question, what does one use for debugging with the later versions of gcc? Surely it isn't necessary to learn all that OMF stuff? (If I did, could I use idebug?)