This is the mail archive of the
mailing list for the Mauve project.
Re: SomeOne posted to me that the Process.exitValue() are ....
- To: Uncle George <gatgul at voicenet dot com>
- Subject: Re: SomeOne posted to me that the Process.exitValue() are ....
- From: Tom Tromey <tromey at cygnus dot com>
- Date: Fri, 12 Nov 1999 20:20:23 -0800 (PST)
- Cc: mauve-discuss at sourceware dot cygnus dot com
- References: <3826BA69.415FF0E2@voicenet.com>
>>>>> ">" == Uncle George <firstname.lastname@example.org> writes:
>> I had originally though that the exit valus of the subprocess would
>> be a composite of system & user exit codes. It appears ( right now
>> ) on the face of it that the user exit code is only returned.
What are the system and user exit codes? I have no idea what you
>> So what does this gotta do with this list ? i'd like to devel a
>> test for process.exitValue(). I suppose this test will be somewhat
>> 'unix' centric.
>> what r my choices.
This is probably hard to do in our framework.
You could try writing a couple of shell scripts, and creating
processes that run them. Then check the exit status of the process
objects. (Or you could just use /bin/true and /bin/false, given that
the scripts will probably be limited to Unix anyway.)
You'd probably want to put a new tag to indicate that this test can
only be run on certain systems ("POSIX" comes to mind).