Re: 'Beep', then exiting with code 255 (0xff)???
From: Programmer Dude (Chris_at_Sonnack.com)
Date: 01/21/05
- Next message: smiyos: "Anyone knows ASP?"
- Previous message: Percival: "Re: Current languages are a mess, what would you choose C#, Java or C++?"
- In reply to: Morten Aune Lyrstad: "Re: 'Beep', then exiting with code 255 (0xff)???"
- Next in thread: Morten Aune Lyrstad: "Re: 'Beep', then exiting with code 255 (0xff)???"
- Reply: Morten Aune Lyrstad: "Re: 'Beep', then exiting with code 255 (0xff)???"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Fri, 21 Jan 2005 11:03:05 -0600
Morten Aune Lyrstad writes:
> Isn't it quite unusual that there is no real error message at all??? I
> mean - I usually get at least a hint of what is wrong. If an object is
> null, one gets an exception. That happens also if you try to do
> something on an object which is already deleted. But I get nothing.
> NOTHING! Except the exit with code 200 bull.
If something in your code throws an exception that you do NOT catch,
the system just aborts (with no error message).
If you can run in a DEBUG environment, you will usually see more
helpful information.
One thing you can try is a try{}catch{} wrapper around the whole program.
Put it in main(), and make sure you catch everything (i.e. catch(...)).
If all else fails, drop into your debugger and "divide and conquor".
Start dividing flow into segments trying to zero in on where the error
is occurring.
Good luck!
- Next message: smiyos: "Anyone knows ASP?"
- Previous message: Percival: "Re: Current languages are a mess, what would you choose C#, Java or C++?"
- In reply to: Morten Aune Lyrstad: "Re: 'Beep', then exiting with code 255 (0xff)???"
- Next in thread: Morten Aune Lyrstad: "Re: 'Beep', then exiting with code 255 (0xff)???"
- Reply: Morten Aune Lyrstad: "Re: 'Beep', then exiting with code 255 (0xff)???"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
