pthread_create segmentation fault with pthread_create.c 552
0
I am getting a segmentation fault right after I am creating a thread. The thread that I am creating is globally defined list. gdb descriptioncode Stdout does not print the print statement right after pthread_create. Would appreciate any help
c multithreading
asked Nov 22 '18 at 3:28
treatyoselftreatyoself
55
add a comment |
0
I am getting a segmentation fault right after I am creating a thread. The thread that I am creating is globally defined list. gdb descriptioncode Stdout does not print the print statement right after pthread_create. Would appreciate any help
c multithreading
asked Nov 22 '18 at 3:28
treatyoselftreatyoself
55
2
can you edit question with code snippet ? what you doing ? like mcve
– ntshetty
Nov 22 '18 at 3:35
1
Welcome to Stack Overflow. Please read the About and How to Ask pages now, especially the latter. We'll need an MCVE (Minimal, Complete, and Verifiable example) included in the question; sending us to somewhere offsite in an image isn't OK — we can't copy the code and experiment with it, all else apart.
– Jonathan Leffler
Nov 22 '18 at 3:59
t1is probablyNULL[or points to random memory] on your firstpthread_createcall, as it is the only value you pass in that could cause a segfault, but it's difficult to know without the rest of your code.
– Craig Estey
Nov 22 '18 at 5:50
Thank you all for the suggestions. Will be better in the future. @CraigEstey You were right. I forgot to malloc what t1 was equal to. Thank you for pointing this out!
– treatyoself
Nov 23 '18 at 16:34
add a comment |
0
0
0
I am getting a segmentation fault right after I am creating a thread. The thread that I am creating is globally defined list. gdb descriptioncode Stdout does not print the print statement right after pthread_create. Would appreciate any help
c multithreading
asked Nov 22 '18 at 3:28
treatyoselftreatyoself
55
I am getting a segmentation fault right after I am creating a thread. The thread that I am creating is globally defined list. gdb descriptioncode Stdout does not print the print statement right after pthread_create. Would appreciate any help
c multithreading
c multithreading
asked Nov 22 '18 at 3:28
treatyoselftreatyoself
55
asked Nov 22 '18 at 3:28
treatyoselftreatyoself
55
asked Nov 22 '18 at 3:28
treatyoselftreatyoself
55
asked Nov 22 '18 at 3:28
treatyoselftreatyoself
55
asked Nov 22 '18 at 3:28
treatyoselftreatyoself
55
55
2
can you edit question with code snippet ? what you doing ? like mcve
– ntshetty
Nov 22 '18 at 3:35
1
Welcome to Stack Overflow. Please read the About and How to Ask pages now, especially the latter. We'll need an MCVE (Minimal, Complete, and Verifiable example) included in the question; sending us to somewhere offsite in an image isn't OK — we can't copy the code and experiment with it, all else apart.
– Jonathan Leffler
Nov 22 '18 at 3:59
t1is probablyNULL[or points to random memory] on your firstpthread_createcall, as it is the only value you pass in that could cause a segfault, but it's difficult to know without the rest of your code.
– Craig Estey
Nov 22 '18 at 5:50
Thank you all for the suggestions. Will be better in the future. @CraigEstey You were right. I forgot to malloc what t1 was equal to. Thank you for pointing this out!
– treatyoself
Nov 23 '18 at 16:34
add a comment |
2
can you edit question with code snippet ? what you doing ? like mcve
– ntshetty
Nov 22 '18 at 3:35
1
Welcome to Stack Overflow. Please read the About and How to Ask pages now, especially the latter. We'll need an MCVE (Minimal, Complete, and Verifiable example) included in the question; sending us to somewhere offsite in an image isn't OK — we can't copy the code and experiment with it, all else apart.
– Jonathan Leffler
Nov 22 '18 at 3:59
t1is probablyNULL[or points to random memory] on your firstpthread_createcall, as it is the only value you pass in that could cause a segfault, but it's difficult to know without the rest of your code.
– Craig Estey
Nov 22 '18 at 5:50
Thank you all for the suggestions. Will be better in the future. @CraigEstey You were right. I forgot to malloc what t1 was equal to. Thank you for pointing this out!
– treatyoself
Nov 23 '18 at 16:34
2
2
can you edit question with code snippet ? what you doing ? like mcve
– ntshetty
Nov 22 '18 at 3:35
can you edit question with code snippet ? what you doing ? like mcve
– ntshetty
Nov 22 '18 at 3:35
1
1
Welcome to Stack Overflow. Please read the About and How to Ask pages now, especially the latter. We'll need an MCVE (Minimal, Complete, and Verifiable example) included in the question; sending us to somewhere offsite in an image isn't OK — we can't copy the code and experiment with it, all else apart.
– Jonathan Leffler
Nov 22 '18 at 3:59
Welcome to Stack Overflow. Please read the About and How to Ask pages now, especially the latter. We'll need an MCVE (Minimal, Complete, and Verifiable example) included in the question; sending us to somewhere offsite in an image isn't OK — we can't copy the code and experiment with it, all else apart.
– Jonathan Leffler
Nov 22 '18 at 3:59
t1 is probably NULL [or points to random memory] on your first pthread_create call, as it is the only value you pass in that could cause a segfault, but it's difficult to know without the rest of your code.– Craig Estey
Nov 22 '18 at 5:50
t1 is probably NULL [or points to random memory] on your first pthread_create call, as it is the only value you pass in that could cause a segfault, but it's difficult to know without the rest of your code.– Craig Estey
Nov 22 '18 at 5:50
Thank you all for the suggestions. Will be better in the future. @CraigEstey You were right. I forgot to malloc what t1 was equal to. Thank you for pointing this out!
– treatyoself
Nov 23 '18 at 16:34
Thank you all for the suggestions. Will be better in the future. @CraigEstey You were right. I forgot to malloc what t1 was equal to. Thank you for pointing this out!
– treatyoself
Nov 23 '18 at 16:34
add a comment |
0
active
oldest
votes
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%2f53423451%2fpthread-create-segmentation-fault-with-pthread-create-c-552%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%2f53423451%2fpthread-create-segmentation-fault-with-pthread-create-c-552%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
2
can you edit question with code snippet ? what you doing ? like mcve
– ntshetty
Nov 22 '18 at 3:35
1
Welcome to Stack Overflow. Please read the About and How to Ask pages now, especially the latter. We'll need an MCVE (Minimal, Complete, and Verifiable example) included in the question; sending us to somewhere offsite in an image isn't OK — we can't copy the code and experiment with it, all else apart.
– Jonathan Leffler
Nov 22 '18 at 3:59
t1is probablyNULL[or points to random memory] on your firstpthread_createcall, as it is the only value you pass in that could cause a segfault, but it's difficult to know without the rest of your code.– Craig Estey
Nov 22 '18 at 5:50
Thank you all for the suggestions. Will be better in the future. @CraigEstey You were right. I forgot to malloc what t1 was equal to. Thank you for pointing this out!
– treatyoself
Nov 23 '18 at 16:34