| All Forums |
Register |
Login |
Search |
Subscriptions |
My Profile |
Inbox |
| Tool Warehouse |
FAQs |
Resources |
Help |
Member List |
Address Book |
Logout |
|
|
returned status -128
|
Logged in as: Guest |
| Users viewing this topic: none |
|
Login  |
|
|
 returned status -128 - Jul. 5, '03, 11:54:49 AM
|
|
|
yoshitaka
Posts: 2
Joined: Jul. 5, '03,
Status: offline
|
Hi.
I' m experienced with SFU3.0 that " big executables" with
many dlls (like exp.exe for ORACLE8) returns status code
-128 ($status of tcsh).
This happens not always.
Sometimes executed successfully, but sometimes got -128.
When got -128, executing again returns status code 0 (successfully).
Does anyone have experiences like this?
Could you tell me why?
sorry for my broken english.
Thanks in advance.
yoshi.
|
|
|
|
|
RE: returned status -128 - Jul. 6, '03, 11:31:54 PM
|
|
|
Rodney
Posts: 3714
Joined: Jul. 9, '02,
From: /Tools lab
Status: offline
|
Win32 programs are well known for their bad behavior with returned status codes. In the Unix world it' s understood that good programs return a consistant status code. For some reason Win32 programmers rarely seem to understand that this is useful and helpful.
The result is that some Win32 program, regardless of who writes them, often return different status codes even when the result is the same. You cannot trust Win32 status codes to mean anything; you cannot rely on the returned status codes at all.
The size of the program and/or the number of Win32 DLL' s that it uses doesn' t really give an indication about how well the program has been written with regard to status codes.
If you write the Win32 program yourself you can write it with good status codes :-) of course.
The returned status codes will be the same for every shell (tcsh, csh, sh, ksh, bash, etc.).
Rodney
|
|
|
|
|
RE: returned status -128 - Oct. 22, '03, 6:55:46 AM
|
|
|
yoshitaka
Posts: 2
Joined: Jul. 5, '03,
Status: offline
|
Hi, Rodney.
I' m sorry for my too late reply.
> Win32 programs are well known for their bad behavior with returned status codes.
I don' t know that at all, because I usually write programs on Unix.
This is my first time for Windows console application to run on SFU.
I' ll keep in mind of it. Thanks.
> If you write the Win32 program yourself you can write it with good status codes :-) of course.
Yes. I' ll do so :-)
By the way, maybe I can get the meaning of return code -128...
By accident, I forgot to add the directory of dlls to %PATH%.
And then, executing .exe, the OS said that " cannot find the dll" .
I could get the status code -128.
On cmd.exe I do the same instruction, I can get the status code 128 (not -128).
I guess, the returned code -128 means that the OS cannot load dll(s) for any reason.
For my first situation (big executables with many dlls returned status code -128),
the OS cannot load whole dlls for something like memory resource shortage.
Not a big executable but the OS returns the status code -128, I guess...
Adding more memory to the PC and avoiding many users to access the PC at a time,
I have not experienced that situation for now.
Thank you.
Yoshi.
|
|
|
|
 New Messages |
 No New Messages |
 Hot Topic w/ New Messages |
 Hot Topic w/o New Messages |
|
 Locked w/ New Messages |
 Locked w/o New Messages |
|
 Post New Thread
Reply to Message
Post New Poll
Submit Vote
Delete My Own Post
Delete My Own Thread
Rate Posts |
|
|
|
Printable Version
