Hi Ludovic,
   
On Mi, 08 Feb 2006, Ludovic Rousseau wrote:

> > What's ongoing there? Why will the system freeze?
> > As far as I can see in EHDestroyEventHandler() the EHStatusHandlerThread 
> > should
> > be cancelled by setting dwLockId to 0xFFFF. The pthread_detach()
> > (SYS_ThreadDetach()) will be called successfully, but calling the
> > pthread_exit() (SYS_ThreadExit()) will result in holding the whole system.
> 
> A user application should _never_ block the kernel.
> Can you also try with a newer kernel?

Yeah, great work. I updated to kernel 2.6.15 and the freezing stuck-state
vanishes.
But, unfortunately the strange length-value in IFDGetCapabalities was still
available. The gdb-session shows that the right pointer-value to the size of
ucGetData:

[readerfactory.c]
    dwGetSize = sizeof(ucGetData);
    rv = IFDGetCapabilities((sReadersContexts[dwContext]), 
TAG_IFD_SLOTS_NUMBER, &dwGetSize, ucGetData);

was taken. But after stepping into:

[ifdwrapper.c]
LONG IFDGetCapabilities(PREADER_CONTEXT rContext, DWORD dwTag, PDWORD 
pdwLength, PUCHAR pucValue)

the pdwLength-value has _changed_ ?!
I intentionally suspected the '-O2' in the compilation code, some time
valuable for such different behaviour, and indeed, changing to '-O0' let the
code receive the pointer correctly. Disassembly shows quite (obvious)
different code between the optimized and non-optimized path.
So I changed to another host-system with Intel Pentium 4 CPU (the first host
has an Intel Pentium M inside) and there the problem has gone with '-O2',
too.

In fact I have had to interfering problems. The first was a problematic
kernel-version and second a compiler-optimization flaw. 
Hopefully both problems will have been vanished for long time and I can come
back to my initial problem of signing my e-mails with a signtrust.de
certificate under Linux.

Ciao, Georg

> _______________________________________________
> Muscle mailing list
> [email protected]
> http://lists.drizzle.com/mailman/listinfo/muscle
> 
_______________________________________________
Muscle mailing list
[email protected]
http://lists.drizzle.com/mailman/listinfo/muscle

Reply via email to