X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org From: "Dave Korn" To: References: <3759e04c0710040726t61d47d00kb5b5103ed639152f AT mail DOT gmail DOT com> <014f01c80695$9db24960$2e08a8c0 AT CAM DOT ARTIMI DOT COM> <3759e04c0710040804r77c0917cs365e9066f86d29ee AT mail DOT gmail DOT com> Subject: RE: Bad EXE format (error 193) Date: Thu, 4 Oct 2007 16:18:19 +0100 Message-ID: <015f01c80699$cb83e200$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: <3759e04c0710040804r77c0917cs365e9066f86d29ee@mail.gmail.com> Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , 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 16:04, Lynn Winebarger wrote: > On 10/4/07, Dave Korn wrote: >> On 04 October 2007 15:26, Lynn Winebarger wrote: >>> 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. >> > I did not understand. No, the larceny binary (runtime > system/interpreter) won't load at all - it doesn't even make it to the > entry point. Oh, my misunderstanding; I thought that we were talking about the compiled executables /generated by/ the larceny compiler, rather than the actual larceny compiler itself. > I'm more than willing to send the "executable". It > might be something an expert could quickly spot. Or the linker map > output, if that would be useful. Yes, why not; feel free to send them both to me, off list. Can't promise I'll spot anything, but I'll take a look. (My first WAG would be that the sassy assembler does something different from other w32 assemblers and that's where the trouble is coming from). 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/