This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Program exited with code 0303000


Dave Korn wrote:
-----Original Message-----
From: cygwin-owner On Behalf Of Bobby McNulty
Sent: 27 September 2004 18:05


Bobby McNulty wrote:


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


Bobby, your advice is no good.


set CYGWIN_error_start=d:\cygwin\bin\dumper.exe


#1:  That's the wrong environment variable.  You want to set CYGWIN to
contain, among any other options, the text
"error_start=D:\cygwin\bin\dumper.exe".  You told him to set
CYGWIN_error_start, which is a different variable altogether and not used by
cygwin.


that is what it is supposed to be.


#2:  Only when you have a program that is failing with SEGV or some other
kind of fatal exception.  If the program is executing and running to
completion, the error_start setting will never be used.


That is why he is getting the errors.


#3:  He was getting the errors before dumper.exe even came into it, so
setting it wrong couldn't have possible caused the errors.  Go back and read
his original post again.  The reason he is getting errors is because his
program is exiting with a non-zero return value.  It was not caused by
dumper.exe and it will not be diagnosable with dumper.exe.

cheers, DaveK

Contact Oracle. There is where is problem is at, not Cygwin.


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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]