No stacktrace from core dump, no build id can be extracted from the core either












0















I have an application in production that in very unpredictable intervals (sometimes less than once a week, rarely once an hour) produces segfaults.
After first having to set it up to produce core dumps at all, I now have one. However I get no symbols at all, so it's useless.



I tried to compare build-ids with the executable that produced it, even though based on timing I pretty much am certain I have the right one, but even that cannot be extracted it seems.



$ eu-unstrip -n --core /path/to/core
0x7ffd56d9e000+0x1000 a6c873a47c39e0b4c46a8e56aace0675e6d58d33@0x7ffd56d9e7d0 . - linux-vdso.so.1


Which appears to not be the id of the [exe] I saw in examples of this.



Is there anything I can do beyond loading gdb, doing symbol-file /path/to/my/binary and having to accept that this core dump is useless to me?



EDIT:



gdb -ex where produces what looks like a stacktrace. How is that different from running symbol-file ?



I have a few libs that I include as a source files, the rest is dynamically linked.



there is a build id in the exe according to read elf.










share|improve this question

























  • What is the output from: gdb -ex where /path/to/exe /path/to/core? Also, is your application statically linked? Does it have BUILD_ID note in readelf -n /path/to/exe ?

    – Employed Russian
    Nov 22 '18 at 3:41











  • See my EDIT above. Seems that -ex where option seems to do something more useful.

    – Cola_Colin
    Nov 23 '18 at 13:22
















0















I have an application in production that in very unpredictable intervals (sometimes less than once a week, rarely once an hour) produces segfaults.
After first having to set it up to produce core dumps at all, I now have one. However I get no symbols at all, so it's useless.



I tried to compare build-ids with the executable that produced it, even though based on timing I pretty much am certain I have the right one, but even that cannot be extracted it seems.



$ eu-unstrip -n --core /path/to/core
0x7ffd56d9e000+0x1000 a6c873a47c39e0b4c46a8e56aace0675e6d58d33@0x7ffd56d9e7d0 . - linux-vdso.so.1


Which appears to not be the id of the [exe] I saw in examples of this.



Is there anything I can do beyond loading gdb, doing symbol-file /path/to/my/binary and having to accept that this core dump is useless to me?



EDIT:



gdb -ex where produces what looks like a stacktrace. How is that different from running symbol-file ?



I have a few libs that I include as a source files, the rest is dynamically linked.



there is a build id in the exe according to read elf.










share|improve this question

























  • What is the output from: gdb -ex where /path/to/exe /path/to/core? Also, is your application statically linked? Does it have BUILD_ID note in readelf -n /path/to/exe ?

    – Employed Russian
    Nov 22 '18 at 3:41











  • See my EDIT above. Seems that -ex where option seems to do something more useful.

    – Cola_Colin
    Nov 23 '18 at 13:22














0












0








0








I have an application in production that in very unpredictable intervals (sometimes less than once a week, rarely once an hour) produces segfaults.
After first having to set it up to produce core dumps at all, I now have one. However I get no symbols at all, so it's useless.



I tried to compare build-ids with the executable that produced it, even though based on timing I pretty much am certain I have the right one, but even that cannot be extracted it seems.



$ eu-unstrip -n --core /path/to/core
0x7ffd56d9e000+0x1000 a6c873a47c39e0b4c46a8e56aace0675e6d58d33@0x7ffd56d9e7d0 . - linux-vdso.so.1


Which appears to not be the id of the [exe] I saw in examples of this.



Is there anything I can do beyond loading gdb, doing symbol-file /path/to/my/binary and having to accept that this core dump is useless to me?



EDIT:



gdb -ex where produces what looks like a stacktrace. How is that different from running symbol-file ?



I have a few libs that I include as a source files, the rest is dynamically linked.



there is a build id in the exe according to read elf.










share|improve this question
















I have an application in production that in very unpredictable intervals (sometimes less than once a week, rarely once an hour) produces segfaults.
After first having to set it up to produce core dumps at all, I now have one. However I get no symbols at all, so it's useless.



I tried to compare build-ids with the executable that produced it, even though based on timing I pretty much am certain I have the right one, but even that cannot be extracted it seems.



$ eu-unstrip -n --core /path/to/core
0x7ffd56d9e000+0x1000 a6c873a47c39e0b4c46a8e56aace0675e6d58d33@0x7ffd56d9e7d0 . - linux-vdso.so.1


Which appears to not be the id of the [exe] I saw in examples of this.



Is there anything I can do beyond loading gdb, doing symbol-file /path/to/my/binary and having to accept that this core dump is useless to me?



EDIT:



gdb -ex where produces what looks like a stacktrace. How is that different from running symbol-file ?



I have a few libs that I include as a source files, the rest is dynamically linked.



there is a build id in the exe according to read elf.







c++ linux gdb coredump






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 23 '18 at 13:22







Cola_Colin

















asked Nov 19 '18 at 21:05









Cola_ColinCola_Colin

91211




91211













  • What is the output from: gdb -ex where /path/to/exe /path/to/core? Also, is your application statically linked? Does it have BUILD_ID note in readelf -n /path/to/exe ?

    – Employed Russian
    Nov 22 '18 at 3:41











  • See my EDIT above. Seems that -ex where option seems to do something more useful.

    – Cola_Colin
    Nov 23 '18 at 13:22



















  • What is the output from: gdb -ex where /path/to/exe /path/to/core? Also, is your application statically linked? Does it have BUILD_ID note in readelf -n /path/to/exe ?

    – Employed Russian
    Nov 22 '18 at 3:41











  • See my EDIT above. Seems that -ex where option seems to do something more useful.

    – Cola_Colin
    Nov 23 '18 at 13:22

















What is the output from: gdb -ex where /path/to/exe /path/to/core? Also, is your application statically linked? Does it have BUILD_ID note in readelf -n /path/to/exe ?

– Employed Russian
Nov 22 '18 at 3:41





What is the output from: gdb -ex where /path/to/exe /path/to/core? Also, is your application statically linked? Does it have BUILD_ID note in readelf -n /path/to/exe ?

– Employed Russian
Nov 22 '18 at 3:41













See my EDIT above. Seems that -ex where option seems to do something more useful.

– Cola_Colin
Nov 23 '18 at 13:22





See my EDIT above. Seems that -ex where option seems to do something more useful.

– Cola_Colin
Nov 23 '18 at 13:22












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


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53382613%2fno-stacktrace-from-core-dump-no-build-id-can-be-extracted-from-the-core-either%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














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53382613%2fno-stacktrace-from-core-dump-no-build-id-can-be-extracted-from-the-core-either%23new-answer', 'question_page');
}
);

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







這個網誌中的熱門文章

Tangent Lines Diagram Along Smooth Curve

Yusuf al-Mu'taman ibn Hud

Zucchini