Contributions
Re: Duplicate Routines entry/exit
Hi Alex, Yes, that is what I was attempting to do and I got the error message stating that I have duplicate routines. I've attached an image of an example. The function I used is just one that I selected at random.5 years agoPlace AQtime QuestionsAQtime Questions3.9KViews1like3CommentsDuplicate Routines entry/exit
I don't understand. Why can I not Start profiling when entering a function and Stop profiling when exiting the same function? I would think that this would be a very common thing to do. For that matter, why is there a limit of only one anyway? I can think of other use cases, such as where I'd want to stop and generate a report at the exiting of a function. What's up with this? Why the limitation?4KViews0likes5CommentsRe: Generating a UML sequence diagram
Oh great, seems that mobile Chrome has the same problem as desktop IE on this forum where the forum doesn't recognize the CRs passed, making the post one long line. Who is to be contacted for that to be fixed? Super annoying! :-( A11 years agoPlace AQtime QuestionsAQtime Questions5.7KViews0likes0CommentsRe: Generating a UML sequence diagram
Say you have 3 functions, x, y and z and you needed to know what order they were called in from function w. How would you be able to determine that from the function call graph results? It is that functionality that I'm looking for. From what I've seen, the call graph results only indicated how long it took to execute not when it was executed. (As a further complication , it only shows an average, and not how long each call took, but that's not relevant to the functionality in currently looking for, just an observation.) Do you see what I'm getting at Alex? A11 years agoPlace AQtime QuestionsAQtime Questions5.7KViews0likes0CommentsRe: Generating a UML sequence diagram
I don't mean just who called who and how long, but also when and in what order. The reason for the functionality is to do a post mortem analysis of the code path between objects and threads. This includes crashes or just for records so that reexecution of the code isn't necessary. This is especially useful in old complex legacy code where documentation is scarce, but I'm sure would still be useful in non legacy applications too where interactions of an unexpected nature occur frequently or (even better) rarely and are difficult to track statically. Thanks, A11 years agoPlace AQtime QuestionsAQtime Questions5.7KViews0likes0CommentsRe: Generating a UML sequence diagram
That is nice but would be nicer if data could be collected realtime, also allowing resetting of the collected data so that unnecessary data could be dumped. Is there any possiblilty for this to become a real feature in AQtime? A11 years agoPlace AQtime QuestionsAQtime Questions5.7KViews0likes0CommentsRe: How do I compare execution flow between two sources?
So this gives me access to the raw data? Nice. :)11 years agoPlace AQtime QuestionsAQtime Questions3.9KViews0likes0Comments