Contributions
Re: Debug vs. Release profiling
Hi, Right, the profiled dll is unmanaged C++. About the .pdb: When installing the profiled application in debug mode, the pdb is present. We do not have acces to the .pdb in release mode. I understand that without pdb we get less information. But I still can't explain why the debug mode does not "see" the dll level functions, wherease the release sees them. Thank you S.14 years agoPlace AQtime QuestionsAQtime Questions1.7KViews0likes0CommentsDebug vs. Release profiling
Hello, When trying to load a release version of "my.dll", AQTime "sees"the dll level functions (seen by Microsoft's "dependency walker" tool.) When loading the debug version of the same dll, nothing is seen! How can that be explianed? Is there a way that AQTime profiles dlls functions even in debug mode? (More precsiely, it looks like that when loading a debug version of a dll, AQTime looks at the included obj, not at the exported functions. If for whatever reason, there is no obj in the dll, nothing is displayed in debug whereas in release, we can see the dlfunctions) Thank you PS: using Peformance profiler 6.50.498.8614 years agoPlace AQtime QuestionsAQtime Questions11KViews0likes3Comments