Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
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
Message-ID: <415847DC.80002@bellsouth.net>
Date: Mon, 27 Sep 2004 12:03:24 -0500
From: Bobby McNulty <bobbymcn AT bellsouth DOT net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax)
MIME-Version: 1.0
To: Dave Korn <dk AT artimi DOT com>
CC: cygwin AT cygwin DOT com
Subject: Re: Program exited with code 0303000
References: <NUTMEGkRlK1F373DVGs00000104 AT NUTMEG DOT CAM DOT ARTIMI DOT COM>
In-Reply-To: <NUTMEGkRlK1F373DVGs00000104@NUTMEG.CAM.ARTIMI.COM>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

Dave Korn wrote:

>>-----Original Message-----
>>From: cygwin-owner On Behalf Of Dan Osborne
>>Sent: 27 September 2004 12:21
> 
> 
>>Further investigation leads me to dumper.exe. Should this 
>>create a core file
>>that I could examine in gdb then I could investigate further 
>>but adding ...
>>

set CYGWIN_error_start=d:\cygwin\usr\bin\dumper.exe
that is what it is supposed to be.
That is why he is getting the errors.






>>to my cygwin.bat doesn't lead to one being created after my 
>>program exits
>>with code 0303000.
> 
> 
>   Why would you expect it to?  Returning a non-zero error code from main
> (..) isn't remotely the same thing as having a SEGV or other problem that
> would cause a core dump to be generated.
> 
> 
>>Any ideas what I'm doing wrong? 
> 
> 
>   Misunderstanding what dumper.exe does.
>   Misunderstanding what a non-zero return code is.
>   Misunderstanding what conditions cause a corefile to be generated.
> 
> 
>>>Things were fine with Oracle OCI calls but I have now 
>>
>>replaced them with
>>
>>>ODBC calls using the odbc32.dll (having used impdef and 
>>
>>dlltool to create
>>
>>>libodbc32.a) so am suspicious of this element but would 
>>
>>appreciate some
>>
>>>pointers in how to investigate further.
> 
> 
>   So, it used to work, then you changed it, and it stopped working?  I think
> you can fairly safely deduce that your changes were buggy.
> 
>   Either that, or the last line of main (...) reads "return 0x0303000;".
> 
>   Since you've got the code up and running in a debugger, you can set
> breakpoints on abort, exit, and the last line of main, then when it hits one
> you can see for yourself from which point your code is exiting and the
> reason why it's returning a non-zero exit code.
> 
>   BTW, you haven't declared main to return void, have you?  If you try that
> I'll have to set the denizens of comp.lang.c on you......
> 
>     cheers, 
>       DaveK



--
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/