-
Notifications
You must be signed in to change notification settings - Fork 97
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
Segmentation fault RpiZeroW #44
Comments
Hi, Thank you very much for your issue report. It looks like you found an important bug. It's pretty hard to debug a segfault just looking at thousand lines of code, so I would need some additional information:
And finally, paste here the output of the execution. It should tell you where did the segmentation fault occurred. Thanks! |
Starting program: /home/felipe/cpufetch/cpufetch Program received signal SIGSEGV, Segmentation fault. |
Hi, Sorry but that is not enough information to properly track the issue...Can you run cpufetch under valgrind? Steps:
Paste the full output here. It should be clear enough to understand what's happening. |
https://pastebin.com/KJgbikpf |
It looks like this is going to be a hard bug to find. I've just pushed a commit to |
Standard run (with make debug) Valgrind on the way |
https://pastebin.com/2FzSPbZC |
Try again with the latest commit in I expect to solve the "Microarchitecture: Unknown" part with this commit. For the issue of number of cores, I will wait to see the contents of the file I told you about, and I will decide what to do then. |
Did a git pull, make clean, make Here's the result |
Great, the microarchitecture problem is solved, but you forgot to post the contents of the file I mentioned. Would you mind to paste them here? Thanks |
Shoot my bad. I just did a sudo cat /sys/devices/system/cpu/present the result is a 0 |
Whooops! Yes, it makes sense that it contains just a fat 0. The problem is that when I wrote the code to query the number of cores I didn't consider the case of a CPU with just one core, that's why in your case it was not working (Segmentation fault). In the previous commit I just made the code to always report that the CPU has 1 core (I did this for debugging purposes). I have pushed a commit in which the code reports the number of cores again, but considering the case of just one core. So I need you to update again and run the latest commit. Everything should work well. If this is the case, I think we solved the issue! Let me know how it goes. |
worked fine from the bugfix2 branch pulled just now. |
Then I think we can consider the issue solved. Thank you very much for reporting this and help me by running all the tests, I have learned a lot! I will merge the changes into master branch soon. Closing the issue. |
No problem!
…On Wed, Apr 7, 2021, 14:49 Dr-Noob ***@***.***> wrote:
Then I think we can consider the issue solved. Thank you very much for
reporting this and help me by running all the tests, I have learned a lot!
I will merge the changes into master branch soon. Closing the issue.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#44 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFZ35CQASE3S6BP6FV64WPDTHSSKRANCNFSM42L23R4A>
.
|
rPiZeroW.
compiles fine, get a "Segmentation fault" message. nothing else returns. just single line 2 words.
The text was updated successfully, but these errors were encountered: