Magic signature on set_wifi_transmit_power crashes is useless |
|
Issue descriptionLooking at crash: 89fc8e1b00000000 I see: Magic Signature: __libc_do_syscall Stable Signature: raise-9365b514 The actual stack crawl was: 0xf6d6f636 (libc-2.19.so + 0x00016636 ) __libc_do_syscall 0xf6d7f313 (libc-2.19.so -raise.c:56 ) raise 0xf6d802ff (libc-2.19.so -abort.c:89 ) abort 0xf6f78ef9 (libbase-core-395517.so -debugger_posix.cc:249 ) base::debug::BreakDebugger 0xf6f8ca8d (libbase-core-395517.so -logging.cc:755 ) logging::LogMessage::~LogMessage 0xab27c12d (set_wifi_transmit_power -set_wifi_transmit_power.cc:156 ) SetWiFiTransmitPower::SetPowerMode 0xab27b759 (set_wifi_transmit_power -set_wifi_transmit_power.cc:289 ) main 0xf6d6f307 (libc-2.19.so -libc-start.c:285 ) __libc_start_main 0xab27b80f (set_wifi_transmit_power + 0x0000180f ) _start 0xab27c6ff (set_wifi_transmit_power -elf-init.c:87 ) __libc_csu_init 0xf706e9df (ld-2.19.so + 0x0000b9df ) _dl_sort_fini 0xab27b7db (set_wifi_transmit_power -set_wifi_transmit_power.cc:291 ) main === The fact that "SetWiFiTransmitPower::SetPowerMode" wasn't in the signature seems a failure of the signature generation. === I'm not 100% sure who is in charge of this these days, so adding a smattering of folks.
,
Nov 1 2016
@1: Ah, got it. I was confused by the fact that it just had "raise" in it, but I guess the extra hex after it (9365b514) encodes the rest of the crawl... :) |
|
►
Sign in to add a comment |
|
Comment 1 by derat@chromium.org
, Nov 1 2016