mutex error when using C function in C++

[pm100]

Hi,

I'm using a C header and functions under a c++ class. The problem is
when I call the c func, say foo(...) directly under main there is no
problem, when I use it in the class VS debugger takes me to xmtx.c.

MyClass::executeFoo(...) {
foo(...);
}

int main(void) {
foo(...) //no problem
MyClass X;
X.executeFoo(); //problem
....
}
Thanks in advence.

[red floyd]

pm100 wrote:

Hi,

I'm using a C header and functions under a c++ class. The problem is
when I call the c func, say foo(...) directly under main there is no
problem, when I use it in the class VS debugger takes me to xmtx.c.

MyClass::executeFoo(...) {
foo(...);
}

int main(void) {
foo(...) //no problem
MyClass X;
X.executeFoo(); //problem
....
}

1. VS is unknown here.
2. Post the smallest *COMPILABLE* example that demonstrates the problem,
without requiring us to use any third party libraries.

[Rolf Magnus]

pm100 wrote:

Hi,

I'm using a C header and functions under a c++ class. The problem is
when I call the c func, say foo(...) directly under main there is no
problem, when I use it in the class VS debugger takes me to xmtx.c.
What does "VS debugger takes me to xmtx.c" mean? What is xmtx.c? How does
the debugger take you there? What happens in your program instead of foo
being executed?
MyClass::executeFoo(...) {
foo(...);
}

int main(void) {
foo(...) //no problem
MyClass X;
X.executeFoo(); //problem
....
}

Well, from that code fragment and without knowing what actually happens, one
can only guess. Maybe your MyClass has a member function foo() that is
called instead of the global foo(), or foo() is in some namespace that
MyClass doesn't know about.

[pm100]

Smallest compilable code requires tons of dll and header files. xmtx.c
seems to be a mutex related file. I think the problem relates to
multithreaded/single threaded issue.

This is where debugger points in xmtx.c:

_RELIABILITY_CONTRACT
void __CLRCALL_PURE_OR_CDECL _Mtxlock(_Rmtx *_Mtx)
{ /* lock mutex */
#ifdef _M_CEE
System::Threading::Thread::BeginThreadAffinity();
#endif
EnterCriticalSection(_Mtx);
}

Also foo is in C style there is no namespace etc.
"VS debugger takes me to xmtx.c" means programs halts and visual studio
debugger tells where the last call happened.

Thanks again,

[Ben Pope]

pm100 wrote:

Smallest compilable code requires tons of dll and header files. xmtx.c
seems to be a mutex related file. I think the problem relates to
multithreaded/single threaded issue.

Since standard C++ doesn't know anything of xmtx.c or threading, I
suggest you take this somewhere topical.

Ben Pope
--
I'm not just a number. To many, I'm known as a string...

[pm100]

Thanks I'll do that.

[Masoom Shaikh]

is source of foo() is available to you ? if yes make sure you link your
program to same version of C runtime as the foo() has been compiled.

e.g. Microsoft's Visual Studio comes with 6 diffrent version of C
runtime library!