Line by line profiling with instruments
I want to profile a C99 program with the Time Profiler of Apple's Instrument tool. I'm using Apple LLVM version 9.1.0 (clang-902.0.39.2).
This kind of, but the profiling information used to be much more detailed in the past. Specifically, I found the line-by-line "heatmap" in the source code very helpful when going through long functions. I can't seem to access this feature anymore in the current version of Instruments. See the attached screenshot. When clicking on a function on the stack trace window, it shows correctly the line of code that takes up a lot of time. However, this is the only line being highlighted and it only has the information "2366x" attached to it. That is just not very useful when there is nothing to compare it against. Also note the suspicious "0 samples" label on the very bottom.
I assume I'm doing something wrong. But I'm lost as to what it could be. Or did Apple make Instruments less useful?
xcode profiling instruments
add a comment |
I want to profile a C99 program with the Time Profiler of Apple's Instrument tool. I'm using Apple LLVM version 9.1.0 (clang-902.0.39.2).
This kind of, but the profiling information used to be much more detailed in the past. Specifically, I found the line-by-line "heatmap" in the source code very helpful when going through long functions. I can't seem to access this feature anymore in the current version of Instruments. See the attached screenshot. When clicking on a function on the stack trace window, it shows correctly the line of code that takes up a lot of time. However, this is the only line being highlighted and it only has the information "2366x" attached to it. That is just not very useful when there is nothing to compare it against. Also note the suspicious "0 samples" label on the very bottom.
I assume I'm doing something wrong. But I'm lost as to what it could be. Or did Apple make Instruments less useful?
xcode profiling instruments
What is your issue? Are you asking why Instruments is highlighting only one line of code or are you asking what the 2366x means? If you click the gear icon at the top of the source view, you can change the 2366x to show a percentage. It also would help if you explain what you mean by "the profiling information used to be much more detailed in the past".
– Mark Szymczyk
Jan 3 at 1:30
add a comment |
I want to profile a C99 program with the Time Profiler of Apple's Instrument tool. I'm using Apple LLVM version 9.1.0 (clang-902.0.39.2).
This kind of, but the profiling information used to be much more detailed in the past. Specifically, I found the line-by-line "heatmap" in the source code very helpful when going through long functions. I can't seem to access this feature anymore in the current version of Instruments. See the attached screenshot. When clicking on a function on the stack trace window, it shows correctly the line of code that takes up a lot of time. However, this is the only line being highlighted and it only has the information "2366x" attached to it. That is just not very useful when there is nothing to compare it against. Also note the suspicious "0 samples" label on the very bottom.
I assume I'm doing something wrong. But I'm lost as to what it could be. Or did Apple make Instruments less useful?
xcode profiling instruments
I want to profile a C99 program with the Time Profiler of Apple's Instrument tool. I'm using Apple LLVM version 9.1.0 (clang-902.0.39.2).
This kind of, but the profiling information used to be much more detailed in the past. Specifically, I found the line-by-line "heatmap" in the source code very helpful when going through long functions. I can't seem to access this feature anymore in the current version of Instruments. See the attached screenshot. When clicking on a function on the stack trace window, it shows correctly the line of code that takes up a lot of time. However, this is the only line being highlighted and it only has the information "2366x" attached to it. That is just not very useful when there is nothing to compare it against. Also note the suspicious "0 samples" label on the very bottom.
I assume I'm doing something wrong. But I'm lost as to what it could be. Or did Apple make Instruments less useful?
xcode profiling instruments
xcode profiling instruments
asked Jan 2 at 4:22
hannohanno
3,30453769
3,30453769
What is your issue? Are you asking why Instruments is highlighting only one line of code or are you asking what the 2366x means? If you click the gear icon at the top of the source view, you can change the 2366x to show a percentage. It also would help if you explain what you mean by "the profiling information used to be much more detailed in the past".
– Mark Szymczyk
Jan 3 at 1:30
add a comment |
What is your issue? Are you asking why Instruments is highlighting only one line of code or are you asking what the 2366x means? If you click the gear icon at the top of the source view, you can change the 2366x to show a percentage. It also would help if you explain what you mean by "the profiling information used to be much more detailed in the past".
– Mark Szymczyk
Jan 3 at 1:30
What is your issue? Are you asking why Instruments is highlighting only one line of code or are you asking what the 2366x means? If you click the gear icon at the top of the source view, you can change the 2366x to show a percentage. It also would help if you explain what you mean by "the profiling information used to be much more detailed in the past".
– Mark Szymczyk
Jan 3 at 1:30
What is your issue? Are you asking why Instruments is highlighting only one line of code or are you asking what the 2366x means? If you click the gear icon at the top of the source view, you can change the 2366x to show a percentage. It also would help if you explain what you mean by "the profiling information used to be much more detailed in the past".
– Mark Szymczyk
Jan 3 at 1:30
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54001166%2fline-by-line-profiling-with-instruments%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54001166%2fline-by-line-profiling-with-instruments%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
What is your issue? Are you asking why Instruments is highlighting only one line of code or are you asking what the 2366x means? If you click the gear icon at the top of the source view, you can change the 2366x to show a percentage. It also would help if you explain what you mean by "the profiling information used to be much more detailed in the past".
– Mark Szymczyk
Jan 3 at 1:30