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

chromium: "Illegal instruction" error on RPi4/dunfell #772

Open
MaxIhlenfeldt opened this issue Nov 22, 2023 · 4 comments
Open

chromium: "Illegal instruction" error on RPi4/dunfell #772

MaxIhlenfeldt opened this issue Nov 22, 2023 · 4 comments

Comments

@MaxIhlenfeldt
Copy link
Collaborator

See the discussions at #757 and #771.

@MaxIhlenfeldt
Copy link
Collaborator Author

@nrpt-m, I've tried to open the new coredump you uploaded, but it's still failing with the same warnings as last time. What output do you get if you run gdb chromium-bin core and then run bt inside gdb?

If that doesn't give you a useful backtrace, you might need to do a build with DEBUG_BUILD = "1".

@nrpt-m
Copy link
Contributor

nrpt-m commented Nov 22, 2023

@nrpt-m, I've tried to open the new coredump you uploaded, but it's still failing with the same warnings as last time. What output do you get if you run gdb chromium-bin core and then run bt inside gdb?

If that doesn't give you a useful backtrace, you might need to do a build with DEBUG_BUILD = "1".

@MaxIhlenfeldt
Actually gdb was not installed on that rpi4/dunfell image so, will add the gdb and test it again as you suggested.

@nrpt-m
Copy link
Contributor

nrpt-m commented Nov 23, 2023

@MaxIhlenfeldt ,
My rpi4 unit is remotely available so, couldn't login as root and with some user I have tried running gdb on chromium-bin. Please find the attached gdb logs.
chromium-119-dunfell-rpi4-gdb-logs.txt

Please let me know what next to be done for further debugging on this.

@MaxIhlenfeldt
Copy link
Collaborator Author

Please let me know what next to be done for further debugging on this.

Sorry for the late reply. To debug the crash using the coredump, you need to run gdb chromium-bin core, and then the bt command should give you the backtrace of the crash.

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

No branches or pull requests

2 participants