You would get that error if for example you compiled without -lpthread. My thought is that it really did not (re)compile correctly. make will not recompile something if it thinks the executable is "current"
Minor correction. The program wouldn't compile, and the linker would issue an error like:
Here the problem occurs at runtime. Your thought seems correct.
Quote:
Originally Posted by SuperStout
Sorry i didnt post this earlier, but i know why i had that error, it wasnt any compiler error, it was beacuse the way i had that i was creating that thread over and over again in an infinit loop. a litle error in my code but al fixed now. thx anyway.
You may need indeed to fix this additional error. However, it is rather unlikely to have something in common with the problem you have initially reported. Jim's likely right; a clean recompile may have resolved your "undefined symbol" problem.
I have trouble compiling a pthread program on unix system which suppotrs pthreads it gives
unresolved
_pthread_create
_pthread_exit
error.
what to do? (1 Reply)
consider if the thread routine returns any void pointer while calling pthread_join,
the thread resources are freed and the thread will be terminated when the main thread is exit ,that is my assumption whether it is true
how do we find whether the thread is alive or terminated
how do we find... (0 Replies)
When I use some of the pthread functions: pthread_join, pthread_exit they work perfect. But when I look in the pthread.h file I can't seem to find any implementations of the functions...where are they hiding?? (2 Replies)
Hello,
I run my pthread code on Linux with 4 processors. However, the speed up is only 2 times.
The code is about solving equation (G+s(i)C)z(i)=B*us(i), i=1,...,n. Here G,C are m*m matrix, B*us(i) is a m*1 vector and s(i) are n different numbers. I need to solve the equation n times to... (2 Replies)
Hi all,
How can i parallize this code in pthread?
for(round=1;round<=16;round++)
{
Expansion(mid, 17 - round - 1, left);
Expansion(mid, round - 1, right);
round++;
Expansion(right, 17 - round - 1, mid);
Expansion(left, round - 1,mid);
}
Whereby each loop depend on the... (2 Replies)
I am so confused about the user threads and kernel threads.Suppose I created a thread using pthread create call in Linux ,whether it will be a user thread or kernel thread.If it user thread,then how its map to kernel thread.
I heard about the M:1,M:N,1:1 mapping methods.Which method linux is... (1 Reply)
I have a while loop like so:
while (counter (file1));
how can I pass that into a pthread_create()?
I was thinking ...
while(pthread_create(&path, NULL, counter, file));
is that right? (1 Reply)
Discussion started by: l flipboi l
1 Replies
LEARN ABOUT CENTOS
error::pass4
ERROR::PASS4(7stap)ERROR::PASS4(7stap)NAME
error::pass4 - systemtap pass-4 errors
DESCRIPTION
Errors that occur during pass 4 (compilation) have generally only a few causes:
kernel or OS version changes
The systemtap runtime and embedded-C fragments in the tapset library are designed to be portable across a wide range of OS versions.
However, incompatibilities can occur when some OS changes occur, such as kernel modifications that change functions, types, or
macros referenced by systemtap. Upstream builds of systemtap are often quickly updated to include relevant fixes, so try getting or
making an updated build. If the issue persists, report the problem to the systemtap developers.
buggy embedded-C code
Embedded-C code in your own guru-mode script cannot be checked by systemtap, and is passed through verbatim to the compiler. Errors
in such snippets of code may be found during the pass-4 compiler invocation, though may be hard to identify by the compiler errors.
incompatible embedded-C code
The interface standards between systemtap-generated code and embedded-C code occasionally change. For example, before version 1.8,
arguments were passed using macros THIS->foo and THIS->__retvalue but from version 1.8 onward, using STAP_ARG_foo and STAP_RETVALUE.
Adjust your embedded-C code to current standards, or use the stap --compatible=VERSION option to make systemtap use a different one.
GATHERING MORE INFORMATION
It may be necessary to run systemtap with -k or -p3 to examine the generated C code. Increasing the verbosity of pass-4 with an option
such as --vp 0001 can also help pinpoint the problem.
SEE ALSO stap(1),
error::reporting(7stap)ERROR::PASS4(7stap)