Changeset c8d5e06 in rtems-testing for sim-scripts


Ignore:
Timestamp:
Apr 1, 2009, 7:44:24 PM (10 years ago)
Author:
Joel Sherrill <joel.sherrill@…>
Branches:
4.11, 8895273c193787f84c4585a10f6d6aceb3b25dc4
Children:
d64a924
Parents:
6b6a8f1
Message:

2009-04-01 Joel Sherrill <joel.sherrill@…>

  • gdb-sim-run.in, gdb-sim.in: Verify runBSP program is in PATH.
Location:
sim-scripts
Files:
3 edited

Legend:

Unmodified
Added
Removed
  • sim-scripts/ChangeLog

    r6b6a8f1 rc8d5e06  
     12009-04-01      Joel Sherrill <joel.sherrill@OARcorp.com>
     2
     3        * gdb-sim-run.in, gdb-sim.in: Verify runBSP program is in PATH.
     4
    152009-03-23      Joel Sherrill <joel.sherrill@OARcorp.com>
    26
  • sim-scripts/gdb-sim-run.in

    r6b6a8f1 rc8d5e06  
    136136
    137137test ${verbose} = "yes" && echo Using ${runBSP}
     138
     139type ${runBSP}
     140check_status $? "Path appears to be broken (cannot find ${runBSP})"
    138141
    139142## These are faults any BSP may generate.  They are common to RTEMS.
  • sim-scripts/gdb-sim.in

    r6b6a8f1 rc8d5e06  
    3434  exit 1
    3535fi
     36
     37type ${runBSP}
     38check_status $? "Path appears to be broken (cannot find ${runBSP})"
    3639
    3740test_exit()
Note: See TracChangeset for help on using the changeset viewer.