Comments
1 comment
-
Hi Shai,
Yep, the CrystalDecisions assembly gives Profiler a hard time due to the
obfuscation (hiding the actual method names and arguments) of the code in
the DLLs.
We're working on a solution to the problem, but in the meantime you can
seem to get results if you exclude the CrystalDecisions namespace from
what's being profiled. It's not going to do you much good to see it anyway,
since all of the function names are obfuscated.
Regards,
Brian Donahue
Red Gate Technical Support
"Shai Zohar" <shai@forexmanage.com> wrote in message
news:UWuLxKdMEHA.1220@server53...
> I am trying to profile a Windows Application runing Crystal Decisions
> Components within,
>
> Everytime i run the application without getting into the crystal / threads
> section i can see the results, whenever i start running multiple threads /
> using the crystal components the results are empty.
>
> Any ideas?
>
> Shai
>
>
Add comment
Please sign in to leave a comment.
I think this has more to do with the crystal reports API. I'm looking
into that.
Regards,
Brian Donahue
Red Gate Technical Support
"Shai Zohar" <shai@forexmanage.com> wrote in message
news:UWuLxKdMEHA.1220@server53...
> I am trying to profile a Windows Application runing Crystal Decisions
> Components within,
>
> Everytime i run the application without getting into the crystal / threads
> section i can see the results, whenever i start running multiple threads /
> using the crystal components the results are empty.
>
> Any ideas?
>
> Shai
>
>