Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provided 4.0c binary crashes on some systems, but works when rebuilt on that system #25

Closed
CheyenneWills opened this issue Oct 25, 2023 · 3 comments
Assignees

Comments

@CheyenneWills
Copy link
Contributor

Need more information

@CheyenneWills
Copy link
Contributor Author

In issue #21, it was reported that 4.0c crashed with the provided binary, but works when rebuilt.

I need additional information.

  • Any messages provided during the crash
  • the output of /proc/cpu
  • glibc's level.
  • And if possible the location of the crash. This might be possible running gdb and capturing the information when the crash happens.
gdb {path to the provided spitbol binary}
    set args {your program}
    run
    info registers
    bt

@CheyenneWills CheyenneWills self-assigned this Oct 25, 2023
@CheyenneWills
Copy link
Contributor Author

#21 (comment)

@CheyenneWills
Copy link
Contributor Author

Looking at the information that was appended in #21 it appears the problem is with my build environment. The build is a static build and statically includes the stdc library and the math library that was built on my system targeting my native CPU, which appears to include additional instructions than the CPU that is having problems.

I believe that rebuilding using non-static libraries should fix the problem. There has been an issue with spitbol as non-static, but I believe that I've now solved that problem. I will need to do additional testing to verify that the fix I have will work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant