Hello,
i've come across some weird effect about using libmcop in a shared module and
loading that module from an executable thats not linked with libstdc++.
I have append a mini sample that loads a .so which has only one function
exported where it creates a Dispatcher object.
If i don't link libstdc++ with the main executable the program hangs
somewhere in the creation of Dispatcher (usually in flockfile() when it tries
to read from a file like the various .mcopfiles).
Any idea about that, can you verify that behaviour ?
greetings,
norman
ps.: maybe thats related to my stdc++ version. my version reads:
libstdc++-3-libc6.1-2-2.10.0.so, oh and i use the mcop that comes with kde
2.1.1
pps: if i replace the ifstream/getline parts in mcop with fopen/fgets it works
tt.zip
