Compiling with -g does not produce .dSYM
0
I have a C++ program that I am attempting to debug with GDB. Unfortunately GDB cannot find debugging symbols, which I think is because no .dSYM file is produced on compilation. I am compiling on macOS High Sierra with Intel icc, using the -g flag. My understanding is that this should produce debugging symbols. Any suggestions as to why this isn't working would be greatly appreciated.
c++ macos gdb icc
asked Nov 14 '18 at 14:24
crevellcrevell
104113
|
show 1 more comment
0
I have a C++ program that I am attempting to debug with GDB. Unfortunately GDB cannot find debugging symbols, which I think is because no .dSYM file is produced on compilation. I am compiling on macOS High Sierra with Intel icc, using the -g flag. My understanding is that this should produce debugging symbols. Any suggestions as to why this isn't working would be greatly appreciated.
c++ macos gdb icc
asked Nov 14 '18 at 14:24
crevellcrevell
104113
icc manual says:" -g [...] The compiler does not support the generation of debugging information in assemblable files. If you specify the -g option the resulting object file will contain debugging information, but the assemblable file will not." so maybe gdb can not use the debugging symbols in this form. This post suggests using the intel debuggeridbalthough i do not know what an "assembable file" is. Possible duplicate.
– Yastanub
Nov 14 '18 at 14:33
Possible duplicate of Debugging Intel Compiled Project with GDB
– Yastanub
Nov 14 '18 at 14:50
Thanks. I am actually using the Intel version of GDB, so it's strange that it can't find whatever debugging information is produced by the compiler. I have also tried runningdsymutil main -o main.dSYMto extract debugging information from the executable but receive the following warning:warning: no debug symbols in executable (-arch x86_64). It's like the compiler just isn't producing debugging information anywhere.
– crevell
Nov 14 '18 at 14:51
Also, for what it's worth,idbdoes not seem to be supported any more, and has been replaced bygdb-ia.
– crevell
Nov 14 '18 at 14:53
maybe try -debug option
– Yastanub
Nov 14 '18 at 14:54
|
show 1 more comment
0
0
0
I have a C++ program that I am attempting to debug with GDB. Unfortunately GDB cannot find debugging symbols, which I think is because no .dSYM file is produced on compilation. I am compiling on macOS High Sierra with Intel icc, using the -g flag. My understanding is that this should produce debugging symbols. Any suggestions as to why this isn't working would be greatly appreciated.
c++ macos gdb icc
asked Nov 14 '18 at 14:24
crevellcrevell
104113
I have a C++ program that I am attempting to debug with GDB. Unfortunately GDB cannot find debugging symbols, which I think is because no .dSYM file is produced on compilation. I am compiling on macOS High Sierra with Intel icc, using the -g flag. My understanding is that this should produce debugging symbols. Any suggestions as to why this isn't working would be greatly appreciated.
c++ macos gdb icc
c++ macos gdb icc
asked Nov 14 '18 at 14:24
crevellcrevell
104113
asked Nov 14 '18 at 14:24
crevellcrevell
104113
asked Nov 14 '18 at 14:24
crevellcrevell
104113
asked Nov 14 '18 at 14:24
crevellcrevell
104113
asked Nov 14 '18 at 14:24
crevellcrevell
104113
104113
icc manual says:" -g [...] The compiler does not support the generation of debugging information in assemblable files. If you specify the -g option the resulting object file will contain debugging information, but the assemblable file will not." so maybe gdb can not use the debugging symbols in this form. This post suggests using the intel debuggeridbalthough i do not know what an "assembable file" is. Possible duplicate.
– Yastanub
Nov 14 '18 at 14:33
Possible duplicate of Debugging Intel Compiled Project with GDB
– Yastanub
Nov 14 '18 at 14:50
Thanks. I am actually using the Intel version of GDB, so it's strange that it can't find whatever debugging information is produced by the compiler. I have also tried runningdsymutil main -o main.dSYMto extract debugging information from the executable but receive the following warning:warning: no debug symbols in executable (-arch x86_64). It's like the compiler just isn't producing debugging information anywhere.
– crevell
Nov 14 '18 at 14:51
Also, for what it's worth,idbdoes not seem to be supported any more, and has been replaced bygdb-ia.
– crevell
Nov 14 '18 at 14:53
maybe try -debug option
– Yastanub
Nov 14 '18 at 14:54
|
show 1 more comment
icc manual says:" -g [...] The compiler does not support the generation of debugging information in assemblable files. If you specify the -g option the resulting object file will contain debugging information, but the assemblable file will not." so maybe gdb can not use the debugging symbols in this form. This post suggests using the intel debuggeridbalthough i do not know what an "assembable file" is. Possible duplicate.
– Yastanub
Nov 14 '18 at 14:33
Possible duplicate of Debugging Intel Compiled Project with GDB
– Yastanub
Nov 14 '18 at 14:50
Thanks. I am actually using the Intel version of GDB, so it's strange that it can't find whatever debugging information is produced by the compiler. I have also tried runningdsymutil main -o main.dSYMto extract debugging information from the executable but receive the following warning:warning: no debug symbols in executable (-arch x86_64). It's like the compiler just isn't producing debugging information anywhere.
– crevell
Nov 14 '18 at 14:51
Also, for what it's worth,idbdoes not seem to be supported any more, and has been replaced bygdb-ia.
– crevell
Nov 14 '18 at 14:53
maybe try -debug option
– Yastanub
Nov 14 '18 at 14:54
icc manual says:" -g [...] The compiler does not support the generation of debugging information in assemblable files. If you specify the -g option the resulting object file will contain debugging information, but the assemblable file will not." so maybe gdb can not use the debugging symbols in this form. This post suggests using the intel debugger
idb although i do not know what an "assembable file" is. Possible duplicate.– Yastanub
Nov 14 '18 at 14:33
icc manual says:" -g [...] The compiler does not support the generation of debugging information in assemblable files. If you specify the -g option the resulting object file will contain debugging information, but the assemblable file will not." so maybe gdb can not use the debugging symbols in this form. This post suggests using the intel debugger
idb although i do not know what an "assembable file" is. Possible duplicate.– Yastanub
Nov 14 '18 at 14:33
Possible duplicate of Debugging Intel Compiled Project with GDB
– Yastanub
Nov 14 '18 at 14:50
Possible duplicate of Debugging Intel Compiled Project with GDB
– Yastanub
Nov 14 '18 at 14:50
Thanks. I am actually using the Intel version of GDB, so it's strange that it can't find whatever debugging information is produced by the compiler. I have also tried running
dsymutil main -o main.dSYM to extract debugging information from the executable but receive the following warning: warning: no debug symbols in executable (-arch x86_64). It's like the compiler just isn't producing debugging information anywhere.– crevell
Nov 14 '18 at 14:51
Thanks. I am actually using the Intel version of GDB, so it's strange that it can't find whatever debugging information is produced by the compiler. I have also tried running
dsymutil main -o main.dSYM to extract debugging information from the executable but receive the following warning: warning: no debug symbols in executable (-arch x86_64). It's like the compiler just isn't producing debugging information anywhere.– crevell
Nov 14 '18 at 14:51
Also, for what it's worth,
idb does not seem to be supported any more, and has been replaced by gdb-ia.– crevell
Nov 14 '18 at 14:53
Also, for what it's worth,
idb does not seem to be supported any more, and has been replaced by gdb-ia.– crevell
Nov 14 '18 at 14:53
maybe try -debug option
– Yastanub
Nov 14 '18 at 14:54
maybe try -debug option
– Yastanub
Nov 14 '18 at 14:54
|
show 1 more 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
);
);
draft saved
draft discarded
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%2f53302437%2fcompiling-with-g-does-not-produce-dsym%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
draft saved
draft discarded
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.
draft saved
draft discarded
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%2f53302437%2fcompiling-with-g-does-not-produce-dsym%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
icc manual says:" -g [...] The compiler does not support the generation of debugging information in assemblable files. If you specify the -g option the resulting object file will contain debugging information, but the assemblable file will not." so maybe gdb can not use the debugging symbols in this form. This post suggests using the intel debugger
idbalthough i do not know what an "assembable file" is. Possible duplicate.– Yastanub
Nov 14 '18 at 14:33
Possible duplicate of Debugging Intel Compiled Project with GDB
– Yastanub
Nov 14 '18 at 14:50
Thanks. I am actually using the Intel version of GDB, so it's strange that it can't find whatever debugging information is produced by the compiler. I have also tried running
dsymutil main -o main.dSYMto extract debugging information from the executable but receive the following warning:warning: no debug symbols in executable (-arch x86_64). It's like the compiler just isn't producing debugging information anywhere.– crevell
Nov 14 '18 at 14:51
Also, for what it's worth,
idbdoes not seem to be supported any more, and has been replaced bygdb-ia.– crevell
Nov 14 '18 at 14:53
maybe try -debug option
– Yastanub
Nov 14 '18 at 14:54