X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f X-Received: by 10.152.1.37 with SMTP id 5mr6013801laj.3.1387098402453; Sun, 15 Dec 2013 01:06:42 -0800 (PST) Date: Sun, 15 Dec 2013 10:06:41 +0100 From: Mateusz Viste User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 Newsgroups: comp.os.msdos.djgpp Subject: Re: Watt32 crashing on i386 References: <52a72357$0$3635$426a74cc AT news DOT free DOT fr> <8ab75766-10f6-4999-bd48-34e812c6c3bd AT googlegroups DOT com> In-Reply-To: <8ab75766-10f6-4999-bd48-34e812c6c3bd@googlegroups.com> Lines: 92 Message-ID: <52ad7122$0$2914$426a34cc@news.free.fr> Organization: Guest of ProXad - France NNTP-Posting-Date: 15 Dec 2013 10:06:42 CET NNTP-Posting-Host: 82.225.72.113 X-Trace: 1387098402 news-4.free.fr 2914 82.225.72.113:64684 X-Complaints-To: abuse AT proxad DOT net Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Bytes: 3758 To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Hi, Just to say thanks :) The latest "386libwatt" port you did recently works fine on a pre-pentium machine. I see it wasn't enough to just recompile it with -march=i386 as I did it, because watt32 itself seems to be buggy itself in regard of older (386/486) CPUs... Thanks! I am still not sure however about the need of compiling it under an older gcc.. What makes me wonder, is that I use the stock gcc as packaged with DJGPP 2.03 (gcc v4.7.1), I compile my program with it (just passing -march=i386), and still it works fine on old CPUs.. Is there any way I could verify myself the opcodes present in a binary file outputted by DJGPP (other than analyzing it for hours in a debugger of course)? cheers, Mateusz On 12/12/2013 02:06 PM, Juan Manuel Guerrero wrote: > Am Dienstag, 10. Dezember 2013 15:21:11 UTC+1 schrieb Mateusz Viste: >> Hi there, >> >> >> >> I have some troubles using watt32 with DJGPP. I have two applications >> >> that work fine on a pentium-grade machine, but both crash on a i386 when >> >> the Watt32 lib is called. >> >> >> >> At first I though that it is because I was using a Watt32 lib compiled >> >> for Pentium (the Watt32 identification string was saying '(Pent)'), so >> >> then I added -march=i386 when compiling Watt32, unfortunately the >> >> applications are still crashing (with a SIGSEGV, General Protection >> >> Fault to be exact). >> >> >> >> The ident. string of the Watt32 build I am using now is this: >> >> >> >> Watt-32 (2.2.10), GNU-C 4.7.1 (386), djgpp 2.03, Dec 9 2013 >> >> >> >> Am I alone with that problem? Or maybe - by any chance - anyone already >> >> noticed this and would be kind enough to point me in the right direction? :) >> >> >> >> Or - have anyone already seen Watt32 working on a 386-class PC? >> >> >> >> I should add that I don't have an i386 machine myself to test - the >> >> crashes have been reported to me by a user of my program, so I can't >> >> even reproduce the problem at will... This same user says that "wget, >> >> which relies on watTCP works perfectly fine on that machine" - so my >> >> next step will be to try to use WatTCP instead of Watt32, and see if it >> >> changes anything... but I am totally in the dark here. >> >> >> >> cheers, >> >> Mateusz > > > I do not have a i386 to test the code. Your 386 version dies with SIGSEGV. > Can you use bfdsymify to identify the code lines where it crashes? > Is the application available that you try to compile? > > Regards, > Juan M. Guerrero >