首页 > 其他分享 >wpa_supplicant中产生__cfi_check错误crash解法

wpa_supplicant中产生__cfi_check错误crash解法

时间:2023-03-20 10:24:05浏览次数:47  
标签:__ 5013 crash 04 23 18 cfi supplicant DEBUG

wifi的crash问题在于以下指定几个wpa会用到的so。wpa该平台是原生的,以下几个s0用原生的就行了。用mtk的hal层的s0会出错我想是因为wpa在mtk的平台不是存原生,加了很多接口以及patch,以及重载了很多原生函数,所以以下的s0能接上mtk平台的wpa。而mtk的wpa放在别的平台,因为这些patch 的修改还牵扯到framwork一些service的启动,直接cp mtk 的wpa到别的平台编译不过。如果能够把相关wpa的patch及framwork层修改移过来,编过,配下面几个s0使用我相信也是能跑起来。    WPA_SUPPLICANT_VERSION := VER_0_8_X BOARD_WPA_SUPPLICANT_DRIVER := NL80211 BOARD_WPA_SUPPLICANT_PRIVATE_LIB := lib_driver_cmd_mtk libwifi-hal-mt66xx BOARD_HOSTAPD_DRIVER := NL80211 BOARD_HOSTAPD_PRIVATE_LIB := lib_driver_cmd_mtk   BOARD_WLAN_DEVICE := MediaTek  

03-04 18:23:49.336 2662 2662 D WifiP2pService: Wifi enabled=true
03-04 18:23:49.337 5010 5010 F libc : Fatal signal 6 (SIGABRT), code -1 (SI_QUEUE) in tid 5010 (wpa_supplicant), pid 5010 (wpa_supplicant)
03-04 18:23:49.368 5013 5013 I crash_dump64: obtaining output fd from tombstoned, type: kDebuggerdTombstoneProto
03-04 18:23:49.369 2393 2393 I tombstoned: received crash request for pid 5010
03-04 18:23:49.370 5013 5013 I crash_dump64: performing dump of process 5010 (target tid = 5010)
03-04 18:23:49.376 5013 5013 E DEBUG : failed to read /proc/uptime: Permission denied
01-01 08:04:30.970 0 0 I [pid:2251,cpu0,logd.reader]logd: logdr: UID=1010 GID=1010 PID=5013 n tail=0 logMask=8 pid=5010 start=0ns deadline=0ns
01-01 08:04:30.976 0 0 I [pid:2251,cpu0,logd.reader]logd: logdr: UID=1010 GID=1010 PID=5013 n tail=0 logMask=1 pid=5010 start=0ns deadline=0ns
03-04 18:23:49.482 5013 5013 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
03-04 18:23:49.482 5013 5013 F DEBUG : Build fingerprint: 'huanglong/tv_hi3751v811/tv:12/SP1A.210812.016/eng.bubble.20230304.175735:userdebug/dev-keys'
03-04 18:23:49.482 5013 5013 F DEBUG : Revision: '0'
03-04 18:23:49.482 5013 5013 F DEBUG : ABI: 'arm64'
03-04 18:23:49.482 5013 5013 F DEBUG : Timestamp: 2023-03-04 18:23:49.374492688+0800
03-04 18:23:49.482 5013 5013 F DEBUG : Process uptime: 0s
03-04 18:23:49.482 5013 5013 F DEBUG : Cmdline: /system/vendor/bin/hw/wpa_supplicant -ip2p0 -Dnl80211 -c/data/vendor/wifi/wpa/p2p_supplicant.conf -I/vendor/etc/wifi/p2p_supplicant_overlay.conf -e/data/misc/wifi/entropy.bin -puse_p2p_group_interface=0 -N -iwlan0 -Dnl80211 -c/data/vendor/wifi/wpa/wpa_supplicant.conf -O/data/vendor/wifi/wpa/sockets -g@android:wpa_wlan0
03-04 18:23:49.482 5013 5013 F DEBUG : pid: 5010, tid: 5010, name: wpa_supplicant >>> /system/vendor/bin/hw/wpa_supplicant <<<
03-04 18:23:49.482 5013 5013 F DEBUG : uid: 1010
03-04 18:23:49.482 5013 5013 F DEBUG : tagged_addr_ctrl: 0000000000000001
03-04 18:23:49.482 5013 5013 F DEBUG : signal 6 (SIGABRT), code -1 (SI_QUEUE), fault addr --------
03-04 18:23:49.482 5013 5013 F DEBUG : x0 0000000000000000 x1 0000000000001392 x2 0000000000000006 x3 0000007ff5c439f0
03-04 18:23:49.482 5013 5013 F DEBUG : x4 4550535553544553 x5 4550535553544553 x6 4550535553544553 x7 312045444f4d444e
03-04 18:23:49.482 5013 5013 F DEBUG : x8 00000000000000f0 x9 0000006fdcd660b0 x10 ffffff00ffffffdf x11 0000000000000001
03-04 18:23:49.482 5013 5013 F DEBUG : x12 4e45505355535445 x13 00312045444f4d44 x14 0000000000081fb4 x15 0000000000400000
03-04 18:23:49.482 5013 5013 F DEBUG : x16 0000006fdce06050 x17 0000006fdcde2700 x18 0000006fee414000 x19 00000000000000ac
03-04 18:23:49.482 5013 5013 F DEBUG : x20 0000000000001392 x21 00000000000000b2 x22 0000000000001392 x23 00000000ffffffff
03-04 18:23:49.483 5013 5013 F DEBUG : x24 0000006fed4f5010 x25 b400006d62e2a161 x26 0000000000000000 x27 0000000000000002
03-04 18:23:49.483 5013 5013 F DEBUG : x28 0000005a922ca700 x29 0000007ff5c43a70
03-04 18:23:49.483 5013 5013 F DEBUG : lr 0000006fdcd93efc sp 0000007ff5c439d0 pc 0000006fdcd93f2c pst 0000000000000000
03-04 18:23:49.483 5013 5013 F DEBUG : backtrace:
03-04 18:23:49.483 5013 5013 F DEBUG : #00 pc 000000000004ff2c /apex/com.android.runtime/lib64/bionic/libc.so (abort+180) (BuildId: ac3d0baaacdc7c6cdebcc4f2fe5705dd)
03-04 18:23:49.483 5013 5013 F DEBUG : #01 pc 00000000000d69fc /vendor/bin/hw/wpa_supplicant (__cfi_check_fail+36) (BuildId: b30cf94f734256f3e0cc2842ec0f7f74)
03-04 18:23:49.483 5013 5013 F DEBUG : #02 pc 00000000000e4dc8 /vendor/bin/hw/wpa_supplicant (__cfi_check+28104) (BuildId: b30cf94f734256f3e0cc2842ec0f7f74)
03-04 18:23:49.483 5013 5013 F DEBUG : #03 pc 00000000002a27bc /vendor/bin/hw/wpa_supplicant ((anonymous namespace)::doZeroArgDriverCommand(wpa_supplicant*, char const*)+180) (BuildId: b30cf94f734256f3e0cc2842ec0f7f74)
03-04 18:23:49.483 5013 5013 F DEBUG : #04 pc 000000000029f2ac /vendor/bin/hw/wpa_supplicant (android::hardware::Return<void> android::hardware::wifi::supplicant::V1_4::implementation::hidl_return_util::validateAndCall<android::hardware::wifi::supplicant::V1_4::implementation::StaIface, android::hardware::wifi::supplicant::V1_0::SupplicantStatusCode, android::hardware::wifi::supplicant::V1_0::SupplicantStatus (android::hardware::wifi::supplicant::V1_4::implementation::StaIface::*)(bool), android::hardware::wifi::supplicant::V1_0::SupplicantStatus, bool&>(android::hardware::wifi::supplicant::V1_4::implementation::StaIface*, android::hardware::wifi::supplicant::V1_0::SupplicantStatusCode, android::hardware::wifi::supplicant::V1_0::SupplicantStatus (android::hardware::wifi::supplicant::V1_4::implementation::StaIface::*&&)(bool), std::__1::function<void (android::hardware::wifi::supplicant::V1_0::SupplicantStatus const&)> const&, bool&)+180) (BuildId: b30cf94f734256f3e0cc2842ec0f7f74)
03-04 18:23:49.483 5013 5013 F DEBUG : #05 pc 000000000029be30 /vendor/bin/hw/wpa_supplicant (android::hardware::wifi::supplicant::V1_4::implementation::StaIface::setSuspendModeEnabled(bool, std::__1::function<void (android::hardware::wifi::supplicant::V1_0::SupplicantStatus const&)>)+64) (BuildId: b30cf94f734256f3e0cc2842ec0f7f74)
03-04 18:23:49.483 5013 5013 F DEBUG : #06 pc 0000000000114430 /vendor/lib64/[email protected] (android::hardware::wifi::supplicant::V1_0::BnHwSupplicantStaIface::_hidl_setSuspendModeEnabled(android::hidl::base::V1_0::BnHwBase*, android::hardware::Parcel const&, android::hardware::Parcel*, std::__1::function<void (android::hardware::Parcel&)>)+288) (BuildId: b90cc86b9ee425044e396ca061baddfb)
03-04 18:23:49.483 5013 5013 F DEBUG : #07 pc 00000000000b916c /vendor/lib64/[email protected] (android::hardware::wifi::supplicant::V1_4::BnHwSupplicantStaIface::onTransact(unsigned int, android::hardware::Parcel const&, android::hardware::Parcel*, unsigned int, std::__1::function<void (android::hardware::Parcel&)>)+2052) (BuildId: 53f631a0092eb80370d72905d40581f0)
03-04 18:23:49.483 5013 5013 F DEBUG : #08 pc 0000000000076db0 /apex/com.android.vndk.v31/lib64/libhidlbase.so (android::hardware::BHwBinder::transact(unsigned int, android::hardware::Parcel const&, android::hardware::Parcel*, unsigned int, std::__1::function<void (android::hardware::Parcel&)>)+96) (BuildId: 96252f8502288b1c8ccaac9cd58077aa)
03-04 18:23:49.483 5013 5013 F DEBUG : #09 pc 0000000000075384 /apex/com.android.vndk.v31/lib64/libhidlbase.so (android::hardware::IPCThreadState::getAndExecuteCommand()+1100) (BuildId: 96252f8502288b1c8ccaac9cd58077aa)
03-04 18:23:49.483 5013 5013 F DEBUG : #10 pc 0000000000079680 /apex/com.android.vndk.v31/lib64/libhidlbase.so (android::hardware::IPCThreadState::handlePolledCommands()+24) (BuildId: 96252f8502288b1c8ccaac9cd58077aa)
03-04 18:23:49.483 5013 5013 F DEBUG : #11 pc 00000000000f25e0 /vendor/bin/hw/wpa_supplicant (eloop_run+1536) (BuildId: b30cf94f734256f3e0cc2842ec0f7f74)
03-04 18:23:49.483 5013 5013 F DEBUG : #12 pc 0000000000236888 /vendor/bin/hw/wpa_supplicant (wpa_supplicant_run+120) (BuildId: b30cf94f734256f3e0cc2842ec0f7f74)
03-04 18:23:49.484 5013 5013 F DEBUG : #13 pc 0000000000247908 /vendor/bin/hw/wpa_supplicant (main.cfi+952) (BuildId: b30cf94f734256f3e0cc2842ec0f7f74)
03-04 18:23:49.484 5013 5013 F DEBUG : #14 pc 0000000000048ac8 /apex/com.android.runtime/lib64/bionic/libc.so (__libc_init+96) (BuildId: ac3d0baaacdc7c6cdebcc4f2fe5705dd)
03-04 18:23:49.500 2662 3417 W NativeCrashListener: Couldn't find ProcessRecord for pid 5010
03-04 18:23:49.501 2393 2393 E tombstoned: Tombstone written to: tombstone_01
03-04 18:23:49.511 2662 2808 I BootReceiver: Copying /data/tombstones/tombstone_01 to DropBox (SYSTEM_TOMBSTONE)
03-04 18:23:49.512 2662 2808 I DropBoxManagerService: add tag=SYSTEM_TOMBSTONE isTagEnabled=true flags=0x6
03-04 18:23:49.533 2662 2808 E NativeTombstoneManager: Tombstone's UID (1010) not an app, ignoring

标签:__,5013,crash,04,23,18,cfi,supplicant,DEBUG
From: https://www.cnblogs.com/bubble1223/p/17235366.html

相关文章

  • Vue全局挂载axios
    前言在vue开发过程中我们有时会把需要的一些模块挂载的全局,以便在各个组件或页面中使用。vue2与vue3中全局挂载是有一些不同的。一、全局挂载示例:pandas是基于NumPy的一......
  • 2023-03-20 前端部分开发工具下载链接
    HbuilderXVscode微信开发者工具 ......
  • cssnote
    bfc(BlockFormattingContext)实现bfc方法1.body根元素2.设置浮动,不包括none3.设置定位,absoulte或者fixed4.行内块显示模式,inline-block5.设置overflow,即hidden,auto,s......
  • https://www.cursor.so/
    Cursor|BuildFast GPT-4自动写代码刚刚发布的Cursor编辑器集成了GPT-4接口,我测试了下他生成代码的能力,叹为观止,我尝试了从前端到后段,从纯软到软硬结合,从UE到U......
  • CentOS7官网详细下载教程
    进入CentOS官网下载,我是Windows操作系统,选择的是x86_64(点击x86_64)这里随便选择一个下载源,我选的是:http://mirrors.nju.edu.cn/centos/7.9.2009/isos/x86_64/进入下载源......
  • Flutter Plugin简单开发
    个人博客:http://www.milovetingting.cn新建项目项目结构创建完成后的目录如图所示,其中example是测试工程,用来测试我们写的插件。lib目录下的文件,就是需要具体实......
  • pnpm安装相关内容
    npm全局安装:npminstallpnpm-g 设置源//查看源pnpmconfiggetregistry//切换淘宝源pnpmconfigsetregistryhttps://registry.npmmirror.com/安装如......
  • 密码学SAT入门文献1——Algebraic and Logic Solving Methods for Cryptanalysis
    密码学SAT入门文献2——CDCL(Crypto)SATSolversforCryptanalysis  Abstract Algebraicsolvingofpolynomialsystemsandsatisfiabilityofproposi......
  • java-基础线程机制
     前言,基础线程机制:Executor管理多个异步任务的执行、Daemon守护线程、sleep()、yield() 一、Executor:1.newCachedThreadPool(),一个任务创建一个线程ExecutorServic......
  • EmployeeController类的分页查询page方法
    @GetMapping("/page")publicR<Page>page(intpage,intpageSize,Stringname){log.info("page={},pageSize={},name={}",page,pageSize,name);//构造分页......