Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Message-ID:	<031c01c2373f$a005d7c0$a352a518@samsystem>
From:	"Samuel" <samuel AT socal DOT rr DOT com>
To:	<cygwin AT cygwin DOT com>
References:	<3D41BDDE DOT 20054 DOT 4C6376DA AT localhost> <20020727014743 DOT GA5707 AT redhat DOT com>
Subject:	Re: Mysterious gdb behavior.
Date:	Mon, 29 Jul 2002 13:36:32 -0700
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-MimeOLE:	Produced By Microsoft MimeOLE V6.00.2600.0000

> ----- Original Message -----
> From: "Christopher Faylor" <cgf-cygwin AT cygwin DOT com>
> To: <cygwin AT cygwin DOT com>
> Sent: Friday, July 26, 2002 6:47 PM
> Subject: Re: Mysterious gdb behavior.
>
> Error 193 is a Windows API error.  Specifically, it is
> ERROR_BAD_EXE_FORMAT.  I thought the normal way to find this out was to
> type "net helpmsg 193" but that doesn't work on my W2K system.


For those that have the Windows SDK header files, the following is a copy of
the relevant portion of winerror.h:

//
// MessageId: ERROR_BAD_EXE_FORMAT
//
// MessageText:
//
//  %1 is not a valid Windows NT application.
//
#define ERROR_BAD_EXE_FORMAT             193L



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -