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

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

# RE: Program exited with code 0303000

• From: "Dave Korn" <dk at artimi dot com>
• To: <cygwin at cygwin dot com>
• Date: Mon, 27 Sep 2004 19:25:42 +0100
• Subject: RE: Program exited with code 0303000

> -----Original Message-----
> From: Bobby McNulty
> Sent: 27 September 2004 18:49

right, and you keep on repeating things that you have already been told
don't work.  You don't accurately read the things that are in front of your
face before you reply.  THAT'S WHY I'M GOING TO BE SHOUTING AT YOU QUITE A
LOT IN THIS LETTER, BECAUSE YOU DON'T ACTUALLY LISTEN TO ANYTHING ANYONE
SAYS TO YOU, YOU JUST ASSUME THEY'RE WRONG AND YOU'RE RIGHT AND I HOPE IF I
SHOUT LOTS YOU'LL ACTUALLY BE ABLE TO HEAR ME.

Dan, Bobby doesn't have any idea what he's talking about.  Ignore his
advice.  Every single word of it.

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

> Originally, he set the variable to set Cygwin=error_start=...

Yes, he did, and that is correct.  That is what it is supposed to be,
albeit with the correction that he should have left 'usr' out of the path.

> You are right, it should be
> set error_start=d:\cygwin\bin\dumper.

I DIDNT SAY THAT **AND** IT ISN'T TRUE.

LOOK, IT'S _STILL_ RIGHT UP THERE AT THE TOP OF THE POST.  RIGHT IN FRONT

HERE, LET ME COPY IT FOR YOU SO YOU CAN SEE HOW WRONG YOU ARE:

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

**I** told him to set CYGWIN.  I was RIGHT.

**YOU** told him to set error_start.  You are WRONG.  LOOK:

http://www.cygwin.com/cygwin-ug-net/using-utils.html

"One common way to use dumper is to plug it into cygwin's Just-In-Time
error_start=x:\path\to\dumper.exe
to the CYGWIN environment variable."

> As to the problem in the code,
> He needs to examine his code closely through a text editor.

WHAT?

HOW MUCH MORE RIDICULOUS CAN YOU GET?

HE'S ALREADY RUNNING IT UNDER A DEBUGGER.  HE CAN NOT ONLY READ ALL THE
CODE, HE CAN EXAMINE THE VARIABLES AND SET BREAKPOINTS AND STEP OVER
INSTRUCTIONS AND EVERYTHING ELSE AS WELL.

WHY ON EARTH WOULD YOU SUGGEST SOMETHING SO RIDICULOUS AS TO STOP USING
THE DEBUGGER AND SWITCH BACK TO JUST READING OVER THE CODE IN A TEXT EDITOR?

> SEGV is a segment fault

That's the ONLY thing you've gotten right so far.

>which is caused by placing a char
> where an int
> should be or vice versa. I know. My trek trivia program had
> this problem

You DON'T know.  Just because you once had a program with a SEGV, doesn't
mean you understand what a SEGV is about nor what causes it.  Just to spell
it out for you in REALLY SIMPLE WORDS:

***LOTS*** OF THINGS can cause a SEGV.  NOT JUST ONE.

> for years before I finally fixed it.
> The disk I had had the same error because I did not replace
> the broken
> code with the fixed code.

And saying this is your idea of impressing us with your range of computer
skills?

Phew.  I'm off to get some cough medicine for my sore throat now.

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/



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