Open MaxIhlenfeldt opened 9 months ago
@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, 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 runbt
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.
@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.
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.
See the discussions at #757 and #771.