This is the mail archive of the crossgcc@cygnus.com mailing list for the crossgcc project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
The stdout/stderr stuff is important to diagnose where the failure occurred, but you also need the exit status of the application (the value returned to the OS when exit () is called) so the tests can determine whether a test passed or failed. John Breen wrote: > > From: Scott Howard <scott@objsw.com> > >The other way that might make it easy would be if > >there was a simulator available for the target hardware. > > Could you expand on this a bit? I don't have a simulator, but I do have > my processor connected to an emulator via the BDM port (mc68360). What > results need to be grabbed? Is it just stuff coming out on stdout? Are > stdin or stderr used? > -- > John A. Breen > jab3@hotmail.com > > ______________________________________________________ > Get Your Private, Free Email at http://www.hotmail.com > _______________________________________________ > New CrossGCC FAQ: http://www.objsw.com/CrossGCC > _______________________________________________ > To remove yourself from the crossgcc list, send > mail to crossgcc-request@cygnus.com with the > text 'unsubscribe' (without the quotes) in the > body of the message. _______________________________________________ New CrossGCC FAQ: http://www.objsw.com/CrossGCC _______________________________________________ To remove yourself from the crossgcc list, send mail to crossgcc-request@cygnus.com with the text 'unsubscribe' (without the quotes) in the body of the message.