libunwind crash in armv7a 2017.05.12.083215 |
||||
Issue description
Stack trace:
#0 0xb27b6130 in unw_set_reg () from /usr/local/google/home/bcf/src/master1/out/target/product/chorizo/symbols/root/lib/libunwind.so.1.0
#1 0xb27b737c in _Unwind_VRS_Set () from /usr/local/google/home/bcf/src/master1/out/target/product/chorizo/symbols/root/lib/libunwind.so.1.0
#2 0xb27a9d38 in _Unwind_SetGR (context=context@entry=0xbe94b400, regno=12, val=3197416360)
at /var/tmp/portage/cross-armv7a-cros-linux-gnueabi/gcc-4.9.2-r154/work/gcc-4.9.2/gcc-4.9-build-armv7a-cros-linux-gnueabi/./gcc/include/unwind-arm-common.h:233
#3 0xb27a9d80 in __gnu_Unwind_Backtrace (trace=0xb275375d <backtrace_helper>, trace_argument=0xbe94b644, entry_vrs=<optimized out>)
at /var/tmp/portage/cross-armv7a-cros-linux-gnueabi/gcc-4.9.2-r154/work/gcc-4.9.2/gcc-4.9/libgcc/unwind-arm-common.inc:578
#4 0xb27aa602 in ___Unwind_Backtrace () at /var/tmp/portage/cross-armv7a-cros-linux-gnueabi/gcc-4.9.2-r154/work/gcc-4.9.2/gcc-4.9/libgcc/config/arm/libunwind.S:360
#5 0xb275382a in __GI___backtrace (array=<optimized out>, size=<optimized out>) at ../sysdeps/arm/backtrace.c:105
#6 0xb47744ce in StackTrace () at ../../base/debug/stack_trace_posix.cc:729
#7 0xb4773b56 in WarmUpBacktrace () at ../../base/debug/stack_trace_posix.cc:447
#8 EnableInProcessStackDumping () at ../../base/debug/stack_trace_posix.cc:699
#9 0xb44ec08c in Initialize () at ../../content/app/content_main_runner.cc:641
#10 0xb51eeff2 in Main () at ../../services/service_manager/embedder/main.cc:420
#11 0xb44eb4aa in content::ContentMain(content::ContentMainParams const&) () at ../../content/app/content_main.cc:19
#12 0xb35f3d3e in main () at ../../chromecast/app/cast_main.cc:13
Note that we build chromium components somewhat unconventionally:
- The compiler used is the one included with chromium (third_party/llvm-build/Release+Asserts/bin/clang)
- ar and ld use chromium sdk version
- System libraries use the CrOS SDK versions
,
May 17 2017
I'm guessing this would be resolved by https://bugs.chromium.org/p/chromium/issues/detail?id=705071#c11 ? However, it looks like their aren't any SDK builds from after 5/12: https://pantheon.corp.google.com/storage/browser/chromiumos-sdk/2017/05/
,
May 17 2017
Yes, please recheck once chromiumos-sdk builder is fixed and new SDK builds are posted.
,
May 24 2017
bcf@ Can you verify if the latest SDK builds fixed the problem?
,
May 24 2017
I verified this is fixed on 2017.05.23.115240
,
May 24 2017
,
Feb 5 2018
|
||||
►
Sign in to add a comment |
||||
Comment 1 by bcf@chromium.org
, May 17 2017