For loop error Post: 303043812

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Error in for loop?

Hi, Working on AIX using the following for loop. for a in `find /edi/iTracTEST/sessions -name nohup.out -print` do echo $a done On the command line it works fine, but insert the code in a file and then running it, it does not want to work. I get the following back. ' is not...

2. Shell Programming and Scripting

Error in Loop?

hi friends, i wrote one simple shell script.. in that am using for loop... when i am trying to execute the script.it shows syntax error at for loop line '((' unexpected. #!/bin/ksh ## ##### To find no of files in the directory NOF=`ls -l /root/COMM/LOGS/eds/20081025| wc -l`...

3. UNIX for Dummies Questions & Answers

error in for loop???

Hi, I get the following output 98 -1 98 0 ./get_AB04-time: line 79: ((: i< && 0 !=7 : syntax error: operand expected (error token is "&& 0 !=7 ") I have this part of code. Line 79 is the line of the for loop. echo ${OCCURRENCE} $i_START CASE=0; i_END=${i_START}...

4. Shell Programming and Scripting

Error Using an if Loop Within a While Loop

Hello All, I am having a problem with an �if loop� within a �while loop� in my Korn Shell program. The basic concept of the program is that it searches for the existence of a series of load files in a load directory, and once it finds one of these files, it begins the following process: � Creates...

5. Shell Programming and Scripting

Error with while loop

the program just prints all the command line arguments Getting error in the program error ./hellow: line 13: 0: command not found ./hellow: line 13: 0: command not found below is the program #!/bin/bash num=$# echo $num if then echo "No arguments are passed ." else ...

6. Shell Programming and Scripting

Error in while loop

I have a file Table.out having table name like this Table_Emp Table_Exp Table_Fcr To show first 10 rows .. I' wrtng a script like this .. #!/bin/ksh cat /tmp/table.out|while read -r table vbar1 do <connect to db> then select * from $table limit 10; > /tmp/1.out done ...

7. Shell Programming and Scripting

Getting error in if loop

Hi All, while executing this code ,I'm gettign below Error if_test: line 3: #!/bin/bash if ; then echo "this is aginity;" elif ; then echo "this is informatica;" fi exit

8. Shell Programming and Scripting

Error in loop

This is my first ever bash script. What i wish to achieve is to find all files in current directory except the script file and count lines in each found file. Some thing seems to be wrong with the if statement :confused: Please help why it does not work? and maybe you have some ideas how to improve...

9. Shell Programming and Scripting

Error in for loop

I was trying to implement a nested for do loop to run a perl script. for i in 1 10 50 do for j in 2 12 55 do perl script.pl "$i" "$i" "$j" done done when I implemented it within a shell script, i got the output, but every time j value will 55, or basically the last value of j in...

10. UNIX for Beginners Questions & Answers

Error with for loop

There are two files abc_123.dat and abc_345.dat if at least one file exists then enter into the loop and remove file and exit. In first iteration, deleting files successfully but "else" statement executing after deleting files."else" should execute only if there is no file in the directory....

LEARN ABOUT LINUX

cutter

CUTTER(1)                                                         Cutter's manual                                                        CUTTER(1)

NAME

       cutter - xUnit family unit testing framework for C and C++

SYNOPSIS

       cutter [option ...] test-directory

       cutter --mode=analyze [option ...] log-directory

DESCRIPTION

       Cutter is a xUnit family unit testing framework for C and C++. Cutter provides programmers two important interfaces:

       1.     easy to write API

       2.     easy to debug UI

       Cutter helps programmers to write their new tests, run their existing tests, get feedbacks from ran their tests.

       test-directory is a directory which has test_*.so. test_*.so are searched recursively.

       log-directory is a directory which has Cutter log files. Cutter logs test results when --stream-directory option is specified.

OPTIONS

       --version
              Cutter shows its own version and exits.

       --mode=[test|analyze]
              It specifies run mode. Cutter runs tests when run mode is test. Cutter analyzes test results when run mode is analyze.

              The default is test.

       -s DIRECTORY, --source-directory=DIRECTORY
              Cutter prepends DIRECTORY to file name when test fails. This is for tolls (like Emacs) which have function jumping to error line.

       -t TEST_CASE_NAME, --test-case=TEST_CASE_NAME
              Cutter  runs  test cases that are matched with TEST_CASE_NAME. If TEST_CASE_NAME is surrounded by "/" (e.g. /test_/), TEST_CASE_NAME
              is handled as regular expression.

              This option can be specified n times. In the case, Cutter runs test cases that are matched with any TEST_CASE_NAME. (OR)

       -n TEST_NAME, --name=TEST_NAME
              Cutter runs tests that are matched with TEST_NAME. If TEST_NAME is surrounded by "/" (e.g. /test_/), TEST_NAME is handled as regular
              expression.

              This option can be specified n times. In the case, Cutter runs test that are matched with any TEST_NAME. (OR)

       -m, --multi-thread
              Cutter runs a test case in a new thread.

              The default is off.

       --max-threads=MAX_THREADS
              Run test cases and iterated tests with MAX_THREADS threads concurrently at a maximum. -1 means no limit.

              The default is 10.

       --disable-signal-handling
              Disable  signal  handling that provides aborting test by C-c, provides backtrace on SEGV and so on. If your test target uses signal,
              Cutter's signal handling may cause a problem. In the case, you should disable Cutter's signal handling by this option.

              The default is enabled.

       --test-case-order=[none|name|name-desc]
              It specifies test case order.

              If 'none' is specified, Cutter doesn't sort. If 'name' is specified, Cutter  sorts  test  cases  by  name  in  ascending  order.  If
              'name-desc' is specified, Cutter sorts test cases by name in descending order.

              The default is none.

       --exclude-file=FILE
              Cutter doesn't read FILE on test collecting.

       --exclude-directory=DIRECTORY
              Cutter doesn't search tests under DIRECTORY.

       --fatal-failures
              Cutter treats failures as fatal problem. It means that Cutter stops test run.

              The default is off.

       --keep-opening-modules
              Cutter keeps opening loaded modules to resolve symbols for debugging.

              The default is off.

       --enable-convenience-attribute-definition
              It enables convenience but danger "#{ATTRIBUTE_NAME}_#{TEST_NAME - 'test_' PREFIX}" attribute set function.

              The default is off.

       --stop-before-test
              It  sets  a  breakpoint  immediately before each test. You can dive into test function easily by running cutter on your debugger and
              stepping into the next function.

              The default is off.

       -u[console|gtk], --ui=[console|gtk]
              It specifies UI.

              The default is console UI.

       -v[s|silent|n|normal|v|verbose], --verbose=[s|silent|n|normal|v|verbose]
              It specifies verbose level.

              This option is only for console UI.

       -c[yes|true|no|false|auto], --color=[yes|true|no|false|auto]
              If 'yes' or 'true' is specified, Cutter uses colorized output by escape sequence. If 'no' or 'false' is specified, Cutter never  use
              colorized output. If 'auto' or the option is omitted, Cutter uses colorized output if available.

              This option is only for console UI.

       --pdf-report=FILE
              Cutter outputs a test report to FILE as PDF format.

       --xml-report=FILE
              Cutter outputs a test report to FILE as XML format.

       --stream=[xml]
              It specifies stream backend. Stream backend streams test results.

              There is only XML stream backend for now.

       --stream-fd=FILE_DESCRIPTOR
              It specifies output file descriptor. The XML stream backend streams to FILE_DESCRIPTOR.

              This option is only for XML stream backend.

       --stream-directory=DIRECTORY
              It specifies output directory. The XML stream backend streams to a file under DIRECTORY.

              This option is only for XML stream backend.

       -?, --help
              Cutter shows common options.

       --help-stream
              Cutter shows stream related options.

       --help-report
              Cutter shows report related options.

       --help-ui
              Cutter shows UI related options.

       --help-all
              Cutter shows all options.

EXIT STATUS

       The  exit  status  is  0 if all tests are passed and non-0 otherwise.  Omission test result and notification test result are not treated as
       failure.

FILES

       /usr/local/share/doc/cutter/
              The directory has Cutter documents. e.g. reference manual, tutorial and so on.

EXAMPLE

       In the following example, cutter runs tests under tests/ directory and shows test progress verbosely.
           % cutter -v v test/

       In the following example, test results are saved under logs/ directory:
           % cutter --stream=xml --stream-directory=logs/ test/

SEE ALSO

       GLib's reference manual.

Cutter                                                             February 2011                                                         CUTTER(1)