I am facing a strange error while creating posix threads:
Given below are two snippets of code, the first one works whereas the second one gives a garbage value in the output.
Snippet 1
This works:
--------------
int *threadids;
threadids = (int *) malloc (num_threads * sizeof(int));
... (4 Replies)
Hello, everyone.
I got the following error when I am using awk to analysis some text file:
*** glibc detected *** awk: malloc(): memory corruption: 0x080c67f8 ***
======= Backtrace: =========
/lib/tls/i686/cmov/libc.so.6
/lib/tls/i686/cmov/libc.so.6... (5 Replies)
there seems not to be error in this segment. In some computers, it can work well. But in others, it will give a failure.
why it ocurrs and how to deal with it?
in a function:
if( *ver == NULL ) {
*ver = (vertex *) malloc(sizeof(vertex)); //this line
... (17 Replies)
Hi every body
I have a problem like that "Dynamic linker error" message.
I can't load many of programs in sco unix openserver 5.0.6.
I guess this problem appear after my last effort to install "SCO Development System" package.
How can I fix this problem?
would you please help me ? (1 Reply)
Hi everyone
I am developing an utility.
At some part of it I read directory entries to a dynamic array: struct list
It stores pointers to items: list.entries,
which are structures: struct entry
If a number of files in a directory is greater then number of elements an array was initially... (11 Replies)
Hi All,
I have a simple code which does some computation by matching string patterns.
In brief:
1. The code reads .dat and .txt files.
2. .dat files are huge text files and .txt files contain some important words.
3. I am just doing strstr to find the patterns.
4. The function returns the... (3 Replies)
*** glibc detected *** ./a.out: malloc(): memory corruption (fast):
Posted A minute ago
M trying to make multiway tree and dont know what happend when this part of code get executed:
01void ins(NODE *ptr)
02{
03 //working
04 if(ptr!=NULL)
05 {
06 SNODE *var=NULL;
07 var=(SNODE... (3 Replies)
I am facing a problem of memory corruption. The loop runs for the first time but does not go through the second time. What could be the problem?
for(int z=0;z<2;z++)
{
fp=fopen("poly.dat","r");
/*do something which reads this file into a 2D array*/
fclose(fp);
... (10 Replies)
I am having a problem with shared memory corruption. I have two 86 servers running Solaris 10 (150400-06). One of the servers is accessed by a Sun Ray thin client Version 11.1.3.0.2.6. I login into server one from the thin client. I then ssh -X to server two. When a process that contains a... (2 Replies)
Discussion started by: salerno
2 Replies
LEARN ABOUT OSF1
xstr
xstr(1) General Commands Manual xstr(1)NAME
xstr - Extracts strings from C programs to implement shared strings
SYNOPSIS
xstr [-c] [file | -]
The xstr command maintains a file called strings into which strings in component parts of a large program are hashed.
OPTIONS
Extracts strings from the specified file.
DESCRIPTION
The strings extracted by xstr are replaced with references to this array. This serves to implement shared constant strings, most useful if
they are also read-only.
The following command extracts the strings from the C source in file, replacing string references by expressions of the form (&xstr[num-
ber]) for some number. xstr -c file
The xstr command uses file as input; the resulting C text is placed in the file x.c to then be compiled. The strings from this file are
appended to the strings file if they are not there already. Repeated strings and strings that are suffixes of existing strings do not cause
changes to the file.
If a string is a suffix of another string in the file, but the shorter string is seen first by xstr, both strings are placed in the file
strings.
After all components of a large program are compiled, a file xs.c declaring the common xstr space can be created by a command of the fol-
lowing form: xstr
Compile and load this xs.c file with the rest of the program. Some C compilers may, by default, put strings in a read-only text section.
The xstr command can also be used on a single file. The following command creates files x.c and xs.c as before, without using or affecting
a strings file in the same directory. xstr file
It may be useful to run xstr after the C preprocessor if any macro definitions yield strings or if there is conditional code that contains
strings that may not be needed. The xstr command reads from its standard input when the argument - (dash) is given. An appropriate command
sequence for running xstr after the C preprocessor is as follows: cc -E file.c | xstr -c - cc -c x.c mv x.o file.o
The xstr command does not touch the file strings unless new items are added, thus make can avoid remaking xs.o unless truly necessary.
EXAMPLES
To extract the strings from the C source in the file.c parameter, replacing string references by expressions of the form (&xstr[number]),
enter: xstr -c file
An appropriate declaration of the xstr array is prepended to file. The resulting C text is placed in the file x.c, to then be com-
piled. To declare the common xstr array space in the xs.c file, enter: xstr
FILES
File that contains the extracted strings. Modified C source. C source for definition of array xstr. Temporary file when the xstr command
does not touch strings.
SEE ALSO
Commands: mkstr(1)xstr(1)