Ubuntu 18.04 and Swi-Prolog error
I am using Ubuntu 18.04 64bit
JDK: openjdk-8
SWI-Prolog: 8.0.1 64bit
I install Swi-prolog from PPA.
sudo apt-get install swi-prolog
sudo apt-get install swi-prolog-java
Installation is completed successfully. I want to use JPL in a multithreaded Java application.
When I try to run the JPL example FamilyMT provided in GitHub, Prolog cannot open a new Thread and error happens.
The output of the run.sh in FamilyMT folder.
consult succeeded
spawning client[0]
spawning client[1]
spawning client[2]
#
spawning client[3]# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007f578d1074b2, pid=3007, tid=0x00007f576caf6700
#
# JRE version: OpenJDK Runtime Environment (8.0_191-b12) (build 1.8.0_191-8u191-b12-2ubuntu0.18.04.1-b12)
# Java VM: OpenJDK 64-Bit Server VM (25.191-b12 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C [libswipl.so+0xb34b2] PL_thread_attach_engine+0xe2
#
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# An error report file with more information is saved as:
# /home/kech/Documents/prolog_sources/prolog7.6.4/swipl-devel/packages/jpl/examples/java/FamilyMT/hs_err_pid3007.log
spawning client[4]
spawning client[5]
spawning client[6]
spawning client[7]
spawning client[8]
spawning client[9]
spawning client[10]
spawning client[11]
spawning client[12]
spawning client[13]
spawning client[14]
spawning client[15]
spawning client[16]
spawning client[17]
spawning client[18]
spawning client[19]
#
# If you would like to submit a bug report, please visit:
# http://bugreport.java.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
Aborted (core dumped)
I also tried other versions of Swi-Prolog, as well as building from sources, but nothing different.
I also checked this example in Windows and it worked OK.
Can someone explain why this happen, and what can I do to fix it?
If you want, I can also post the error log that is created from this.
18.04 java openjdk
asked 10 hours ago
KonKostKonKost
1
New contributor
KonKost is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
I am using Ubuntu 18.04 64bit
JDK: openjdk-8
SWI-Prolog: 8.0.1 64bit
I install Swi-prolog from PPA.
sudo apt-get install swi-prolog
sudo apt-get install swi-prolog-java
Installation is completed successfully. I want to use JPL in a multithreaded Java application.
When I try to run the JPL example FamilyMT provided in GitHub, Prolog cannot open a new Thread and error happens.
The output of the run.sh in FamilyMT folder.
consult succeeded
spawning client[0]
spawning client[1]
spawning client[2]
#
spawning client[3]# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007f578d1074b2, pid=3007, tid=0x00007f576caf6700
#
# JRE version: OpenJDK Runtime Environment (8.0_191-b12) (build 1.8.0_191-8u191-b12-2ubuntu0.18.04.1-b12)
# Java VM: OpenJDK 64-Bit Server VM (25.191-b12 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C [libswipl.so+0xb34b2] PL_thread_attach_engine+0xe2
#
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# An error report file with more information is saved as:
# /home/kech/Documents/prolog_sources/prolog7.6.4/swipl-devel/packages/jpl/examples/java/FamilyMT/hs_err_pid3007.log
spawning client[4]
spawning client[5]
spawning client[6]
spawning client[7]
spawning client[8]
spawning client[9]
spawning client[10]
spawning client[11]
spawning client[12]
spawning client[13]
spawning client[14]
spawning client[15]
spawning client[16]
spawning client[17]
spawning client[18]
spawning client[19]
#
# If you would like to submit a bug report, please visit:
# http://bugreport.java.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
Aborted (core dumped)
I also tried other versions of Swi-Prolog, as well as building from sources, but nothing different.
I also checked this example in Windows and it worked OK.
Can someone explain why this happen, and what can I do to fix it?
If you want, I can also post the error log that is created from this.
18.04 java openjdk
asked 10 hours ago
KonKostKonKost
1
New contributor
KonKost is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
I am using Ubuntu 18.04 64bit
JDK: openjdk-8
SWI-Prolog: 8.0.1 64bit
I install Swi-prolog from PPA.
sudo apt-get install swi-prolog
sudo apt-get install swi-prolog-java
Installation is completed successfully. I want to use JPL in a multithreaded Java application.
When I try to run the JPL example FamilyMT provided in GitHub, Prolog cannot open a new Thread and error happens.
The output of the run.sh in FamilyMT folder.
consult succeeded
spawning client[0]
spawning client[1]
spawning client[2]
#
spawning client[3]# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007f578d1074b2, pid=3007, tid=0x00007f576caf6700
#
# JRE version: OpenJDK Runtime Environment (8.0_191-b12) (build 1.8.0_191-8u191-b12-2ubuntu0.18.04.1-b12)
# Java VM: OpenJDK 64-Bit Server VM (25.191-b12 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C [libswipl.so+0xb34b2] PL_thread_attach_engine+0xe2
#
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# An error report file with more information is saved as:
# /home/kech/Documents/prolog_sources/prolog7.6.4/swipl-devel/packages/jpl/examples/java/FamilyMT/hs_err_pid3007.log
spawning client[4]
spawning client[5]
spawning client[6]
spawning client[7]
spawning client[8]
spawning client[9]
spawning client[10]
spawning client[11]
spawning client[12]
spawning client[13]
spawning client[14]
spawning client[15]
spawning client[16]
spawning client[17]
spawning client[18]
spawning client[19]
#
# If you would like to submit a bug report, please visit:
# http://bugreport.java.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
Aborted (core dumped)
I also tried other versions of Swi-Prolog, as well as building from sources, but nothing different.
I also checked this example in Windows and it worked OK.
Can someone explain why this happen, and what can I do to fix it?
If you want, I can also post the error log that is created from this.
18.04 java openjdk
asked 10 hours ago
KonKostKonKost
1
New contributor
KonKost is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I am using Ubuntu 18.04 64bit
JDK: openjdk-8
SWI-Prolog: 8.0.1 64bit
I install Swi-prolog from PPA.
sudo apt-get install swi-prolog
sudo apt-get install swi-prolog-java
Installation is completed successfully. I want to use JPL in a multithreaded Java application.
When I try to run the JPL example FamilyMT provided in GitHub, Prolog cannot open a new Thread and error happens.
The output of the run.sh in FamilyMT folder.
consult succeeded
spawning client[0]
spawning client[1]
spawning client[2]
#
spawning client[3]# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007f578d1074b2, pid=3007, tid=0x00007f576caf6700
#
# JRE version: OpenJDK Runtime Environment (8.0_191-b12) (build 1.8.0_191-8u191-b12-2ubuntu0.18.04.1-b12)
# Java VM: OpenJDK 64-Bit Server VM (25.191-b12 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C [libswipl.so+0xb34b2] PL_thread_attach_engine+0xe2
#
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# An error report file with more information is saved as:
# /home/kech/Documents/prolog_sources/prolog7.6.4/swipl-devel/packages/jpl/examples/java/FamilyMT/hs_err_pid3007.log
spawning client[4]
spawning client[5]
spawning client[6]
spawning client[7]
spawning client[8]
spawning client[9]
spawning client[10]
spawning client[11]
spawning client[12]
spawning client[13]
spawning client[14]
spawning client[15]
spawning client[16]
spawning client[17]
spawning client[18]
spawning client[19]
#
# If you would like to submit a bug report, please visit:
# http://bugreport.java.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
Aborted (core dumped)
I also tried other versions of Swi-Prolog, as well as building from sources, but nothing different.
I also checked this example in Windows and it worked OK.
Can someone explain why this happen, and what can I do to fix it?
If you want, I can also post the error log that is created from this.
18.04 java openjdk
18.04 java openjdk
asked 10 hours ago
KonKostKonKost
1
New contributor
KonKost is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 10 hours ago
KonKostKonKost
1
New contributor
KonKost is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 10 hours ago
KonKostKonKost
1
New contributor
KonKost is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 10 hours ago
KonKostKonKost
1
asked 10 hours ago
KonKostKonKost
1
1
New contributor
KonKost is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
KonKost is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
KonKost is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
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
});
}
});
KonKost is a new contributor. Be nice, and check out our Code of Conduct.
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%2faskubuntu.com%2fquestions%2f1117454%2fubuntu-18-04-and-swi-prolog-error%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
KonKost is a new contributor. Be nice, and check out our Code of Conduct.
KonKost is a new contributor. Be nice, and check out our Code of Conduct.
KonKost is a new contributor. Be nice, and check out our Code of Conduct.
KonKost is a new contributor. Be nice, and check out our Code of Conduct.
Thanks for contributing an answer to Ask Ubuntu!
- 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%2faskubuntu.com%2fquestions%2f1117454%2fubuntu-18-04-and-swi-prolog-error%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
