Hello Markus,
Unfortunately I was not able to detect when a deadlock occurs so as to
launch the function you mention. Let's see if Arno's code will do the
trick...
Best Regards,
SZ
On 4/29/07, Markus Humm <[EMAIL PROTECTED]> wrote:
> Hello,
>
> what I meant by mentioning MadExcept: it contains
Hello,
what I meant by mentioning MadExcept: it contains the source code to
determine the call stack. This you could extract from madExcept and call
it whenever you like. No need to raise some exception first!
The full version of the FastMM memory manager contains similar code.
Greetings
Mark
Dear Arno,
Thank you SO MUCH! I will tell you what the customer reports.
Regards,
SZ
On 4/29/07, Arno Garrels <[EMAIL PROTECTED]> wrote:
> Arno Garrels wrote:
> >
> > Try something like the class below (untested), copy the code
>
> Small fix add "raise" in front of ECriticalSection.Create in
>
Arno Garrels wrote:
>
> Try something like the class below (untested), copy the code
Small fix add "raise" in front of ECriticalSection.Create in
TCriticalSection.Create as well as in TCriticalSection.Release.
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http:/
Fastream Technologies wrote:
> Hello,
>
> So this is my latest code:
>
> void inline __fastcall lockCriticalSection(TCriticalSection
> *criticalSection) {
> for(int i = 0; i < 5000; ++i)
> {
> if(criticalSection->TryEnter())
> return;
Calling Sleep() in such short intervals is critical.
With eac
