| knowledge-database (beta) |
 |
Current group: comp.programming
'Beep', then exiting with code 255 (0xff)???
| Morten Aune Lyrstad | | gswork at mailcity.com | | Morten Aune Lyrstad | | spinoza1111 at yahoo.com | | Morten Aune Lyrstad | | Morten Aune Lyrstad | | Programmer Dude | | Morten Aune Lyrstad |
|
|
| | From: | Morten Aune Lyrstad | | Subject: | 'Beep', then exiting with code 255 (0xff)??? | | Date: | Thu, 20 Jan 2005 21:16:29 +0100 |
|
|
 | What the...
My application gives off a beep, and then exits with this message:
The program '[6620] Win32DevApp.exe: Native' has exited with code 255
(0xff).
No other error messages are seen. What the here> is going on???
It appears to be failing on the deletion of a class object...
Yours,
Morten Aune Lyrstad
|
|
| | From: | gswork at mailcity.com | | Subject: | Re: 'Beep', then exiting with code 255 (0xff)??? | | Date: | 21 Jan 2005 01:26:22 -0800 |
|
|
|
Morten Aune Lyrstad wrote:
> 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.
>
> M
i suppose it is unusual, though the app is exiting - sure there
couldn't be some bug in the program flow?
perhaps someone in a win32 group can help, without knowing what the
error code means and seeing the thing in action it's a bit difficult!
|
|
| | From: | Morten Aune Lyrstad | | Subject: | Re: 'Beep', then exiting with code 255 (0xff)??? | | Date: | Fri, 21 Jan 2005 17:03:07 +0100 |
|
|
| >
>
> i suppose it is unusual, though the app is exiting
Exiting, yes, but directly from a delete, not by normal means...
- sure there
> couldn't be some bug in the program flow?
No, I'm quite sure that there ARE bug(s) in the program flow. I just
don't get any help figuring out where that bug is, just by the exit code
255!
>
> perhaps someone in a win32 group can help, without knowing what the
> error code means and seeing the thing in action it's a bit difficult!
>
Couldn't agree more.
Actually, I made a change in the object reference system, so that
released objects gets deleted differently, and it solved the problem.
I'm guessing that a hWnd was being used even though I did not think so.
So there goes 'so I know that works'... ;-)
|
|
| | From: | spinoza1111 at yahoo.com | | Subject: | Re: 'Beep', then exiting with code 255 (0xff)??? | | Date: | 20 Jan 2005 18:56:04 -0800 |
|
|
|
Morten Aune Lyrstad wrote:
> What the...
>
> My application gives off a beep, and then exits with this message:
>
> The program '[6620] Win32DevApp.exe: Native' has exited with code 255
> (0xff).
>
> No other error messages are seen. What the word
> here> is going on???
>
> It appears to be failing on the deletion of a class object...
Honk snorp. You haven't given much information. But the first place to
look is at the deletion of a "class object". Check whether the "class
object" exists. In C++ is it null (with a handle of 0)? In VB, is it
Nothing? I can well imagine your system honking at you on delete of an
object which does not exist.
"Say something!" "Something!" - Pulp Fiction
>
> Yours,
> Morten Aune Lyrstad
|
|
| | From: | Morten Aune Lyrstad | | Subject: | Re: 'Beep', then exiting with code 255 (0xff)??? | | Date: | Fri, 21 Jan 2005 08:08:04 +0100 |
|
|
| spinoza1111@yahoo.com wrote:
> Morten Aune Lyrstad wrote:
>
>>What the...
>>
>>My application gives off a beep, and then exits with this message:
>>
>>The program '[6620] Win32DevApp.exe: Native' has exited with code 255
>
>
>>(0xff).
>>
>>No other error messages are seen. What the >
> word
>
>>here> is going on???
>>
>>It appears to be failing on the deletion of a class object...
>
>
> Honk snorp. You haven't given much information. But the first place to
> look is at the deletion of a "class object". Check whether the "class
> object" exists. In C++ is it null (with a handle of 0)? In VB, is it
> Nothing? I can well imagine your system honking at you on delete of an
> object which does not exist.
>
> "Say something!" "Something!" - Pulp Fiction
>
>>Yours,
>>Morten Aune Lyrstad
>
>
There isn't much I can say, 'cuz there isn't much I know... ;-) other
than that the object cannot be null, as it has been in use throughout
the entire lifespan of the application (it's a window), and that
it_should_ not be deleted, because it is a reference counted class. The
reference counting system has been tested many times, so I know that works.
And of course, that I program in C++ ;-)
M
|
|
| | From: | Morten Aune Lyrstad | | Subject: | Re: 'Beep', then exiting with code 255 (0xff)??? | | Date: | Fri, 21 Jan 2005 08:10:51 +0100 |
|
|
| 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.
M
|
|
| | From: | Programmer Dude | | Subject: | Re: 'Beep', then exiting with code 255 (0xff)??? | | 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!
|
|
| | From: | Morten Aune Lyrstad | | Subject: | Re: 'Beep', then exiting with code 255 (0xff)??? | | Date: | Sat, 22 Jan 2005 13:37:17 +0100 |
|
|
| Programmer Dude wrote:
> If something in your code throws an exception that you do NOT catch,
> the system just aborts (with no error message).
Now that's something that has NEVER happened to me before. I always run
in a debug environment while I am developing an application. So if there
is an exception that I don't catch, the system aborts, yes, but WITH an
"uncaught exception" error, plus a pointer to where the exception occurred.
>
> If you can run in a DEBUG environment, you will usually see more
> helpful information.
See above ;-)
>
> 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!
>
Thanks! :-)
|
|
|
| | |
|
 |