Just to confirm, using RS="" was to read in stanzas - groups of lines separated by blank lines. Or are you trying to read in the entire file at once? The latter is what you are trying to do with:
which really should be:
This is because xargs will join the lines of text until the maximum number of arguments or maximum command line length is reached.
Perl's file slurping may be useful here:
which generates:
for the followig input file: ---------- Post updated at 01:34 PM ---------- Previous update was at 01:31 PM ----------
Or if you don't mind each indice being on a separate line, this is slightly simpler:
Hello To All!
Now anfd then I receive a message on my console:
Segmentation fault (core dumped)
What does it mean? Or more precisely what are the implications?
:confused: (1 Reply)
Hai!
i am working on Digital UNIX V3.2c Work station, my program uses Pro*C, C and X-Motif calls. i am facing problem while running application saying "Illegal Instruction Core Dumped".
debugger dbx shows error at a line which shows "noname". when commenting large portion of the code it runs... (1 Reply)
why tell core dumped?
I am a new .I write a program.I use cc to complier it.
when i run it,it tell me "core dumped"?
who can tell me the reason?
the program as follow:
main()
{
char *a;
printf("please input your name:");
scanf("%s",a);
printf("\n");
printf("%s",a);
} (3 Replies)
i am getting Segmentation Fault (core dumped) on solaris,
but when i run the same program with same input on linux it runs successfully.
How can i trace the fault in program on solaris. (6 Replies)
i am getting segmentation fault (core dumped)
i tried following things but couldn't understand what is wrong with my prog and where the problem is....
i have only adb debugger available on solaris....
so plz help
bash-3.00$ pstack core
core 'core' of 765: ./mod_generalised_tapinread... (4 Replies)
Hi All,
I am getting "Segmentation fault (core dumped)" error in the runtime. I am new this please can you tell me why is that i am getting this error and I am not sure of my compilation :
gcc -c avc_test.c
gcc -c md5.c
gcc avc_test.o md5.o -shared -Llibcoreavc_sdk.so -o proj
... (1 Reply)
When I was trying to mirror in my v880 server after OS up gradation from 8 to 10
metadb -afc 3 /dev/dsk/c1t1d0s7
I got an error
metadb: Segmentation Fault
Segmentation Fault (core dumped)
Then I logged a case to Oracle/sun team they suggest
"Please could you try
metadb -ac 3... (0 Replies)
Can anyone tell me why I keep getting a Segmentation fault when I try to run tilda?
$ tilda
Segmentation fault (core dumped)
It seemed to run after I deleted my tilda directory like this thread said to do. Unfortunately it wouldn't let me set my keybinding with anything I tried.
... (0 Replies)
Discussion started by: cokedude
0 Replies
LEARN ABOUT REDHAT
for
for(n) Tcl Built-In Commands for(n)
__________________________________________________________________________________________________________________________________________________NAME
for - ``For'' loop
SYNOPSIS
for start test next body
_________________________________________________________________DESCRIPTION
For is a looping command, similar in structure to the C for statement. The start, next, and body arguments must be Tcl command strings,
and test is an expression string. The for command first invokes the Tcl interpreter to execute start. Then it repeatedly evaluates test
as an expression; if the result is non-zero it invokes the Tcl interpreter on body, then invokes the Tcl interpreter on next, then repeats
the loop. The command terminates when test evaluates to 0. If a continue command is invoked within body then any remaining commands in
the current execution of body are skipped; processing continues by invoking the Tcl interpreter on next, then evaluating test, and so on.
If a break command is invoked within body or next, then the for command will return immediately. The operation of break and continue are
similar to the corresponding statements in C. For returns an empty string.
Note: test should almost always be enclosed in braces. If not, variable substitutions will be made before the for command starts execut-
ing, which means that variable changes made by the loop body will not be considered in the expression. This is likely to result in an
infinite loop. If test is enclosed in braces, variable substitutions are delayed until the expression is evaluated (before each loop iter-
ation), so changes in the variables will be visible. For an example, try the following script with and without the braces around $x<10:
for {set x 0} {$x<10} {incr x} {
puts "x is $x"
}
SEE ALSO
break, continue, foreach, while
KEYWORDS
for, iteration, looping
Tcl for(n)