IdeasAll Idea StatusesNew IdeaTagged:TagTrendingLet people know if a profiling run had profiling disabled for the entire run. This came from the discussion at: https://community.smartbear.com/t5/AQtime/Why-is-Performance-Profiler-indicating-no-routines-analyzed/td-p/149121 I lost about an hour wondering why I kept get...Coverage profiler also takes compiled instruction code plausibility into account. Background: sometimes a compiler (MSVC) would generate unreachable instruction code (eventually in none-optimized case) and Coverage Profiler is still counting such unreachable instruction code as un...Light Coverage Results: Merge routing results regardsless of the template parameter The results of the "Light Coverage" profiler should merge the results of all routines with different template parameters. Let's say, you have code like the example below. When you profile the app...Provide line info when a routine is marked as "Unsafe" When AQTime detects a routine to be unsafe, it would be very helpful if AQTime could tell the line number that causes the code to be unsafe. I have spent quite a lot of time breaking down a fairly...Add support for multiple actions in the same method While using AQTime Pro, I was trying to use Actions within AQTime to periodically capture fresh snapshots of my application. I am basically setting up an action to Get Results when method FOO is ...Intel Visual FORTRAN support Dear all, I strongly suggest that, in the next future, AQtime supports not only Compaq Visual FORTRAN but also the de facto standard for FORTRAN programming: Intel Visual FORTRAN, Profile multiple processes We often have the problem that we want to profile executables, which are started indirectly by another executable, for example: A.EXE is starting B.EXE and B.EXE is the process, which shall be prof...Support Fibers API Currently, Performance Profiler causes program crash when profiling code using Fibers API (see Case #00169159: Program halts when run under Performance Profiler). To reproduce: 1) Compile atta...Ignore unreachable code in code coverage reports We are using the "Light Coverage Profiler" with "collect info about lines: on" for creating coverage reports of our unit tests. Let's say, you have C++ code like this: Header: __declspec(nore...Want link from Log Item to the Test Item After a test runs and I am looking at the log, I am able to look at the Call Stack or the Message and link to the Test. That's great! But, almost every time, I also want to resume the test run ...
