X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
From: "Dave Korn" <dave DOT korn AT artimi DOT com>
To: <cygwin AT cygwin DOT com>
References: <3759e04c0710040726t61d47d00kb5b5103ed639152f AT mail DOT gmail DOT com>
Subject: RE: Bad EXE format (error 193)
Date: Thu, 4 Oct 2007 15:48:24 +0100
Message-ID: <014f01c80695$9db24960$2e08a8c0@CAM.ARTIMI.COM>
MIME-Version: 1.0
Content-Type: text/plain; 	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <3759e04c0710040726t61d47d00kb5b5103ed639152f@mail.gmail.com>
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

On 04 October 2007 15:26, Lynn Winebarger wrote:


>>> you see an error message along those lines, yes?  Hm.  Does it still
>>> happen if you compile the most basic sort of "hello world" program?
>> 
>> 
>>   It might also be informative to run "cygcheck <path-to-exe>" on your
>> compiled executable; that'll display the dependent DLLs for you.  A bit of
>> googling suggests that 193 can be caused by a corrupt/bogus executable, but
>> equally by a good executable thatt depends on a DLL which is faulty.
>> 
> 
> Thanks, Dave.  I did compile a hello-world.c program, and it ran, but
> I had also compiled PLT scheme v360 before (needed to bootstrap
> Larceny) and had run it without problem as well (I had thought this
> might be a permission issue, because what bash actually reports is
> "Access denied" - the underlying error took further investigation)

  Actually, I was trying to ask if you'd compiled a basic "helloworld" with
your new larceny compiler, or indeed if this example of yours is already a
very simple test program; i.e. is it only complex larceny executables that
don't work, or even the very simplest ones.

> $ cygcheck ./larcenybin.exe
> .\larcenybin.exe
>   C:\cygwin\bin\cygwin1.dll
>     C:\WINDOWS\system32\ADVAPI32.DLL
>       C:\WINDOWS\system32\ntdll.dll
>       C:\WINDOWS\system32\KERNEL32.dll
>       C:\WINDOWS\system32\RPCRT4.dll

  Unfortunately that all looks completely correct, no clues there.

    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/