P3: Somewhat important We have an Android project with a native lib dependency with a lot of rxcpp in it, which is crashing gdb when launching the debug session. It is due to a number of rxcpp symbols which can't be demangled by gdb. To reproduce this, you can run the following with the most recent gdb (8.2.1 at the time of writing):
gdb -ex "demangle -l c++ _ZN5rxcpp10subscriberIbNS_8observerIbNS_9operators6detail6filterIbZZN12pppppppppppp6pppppp17require_one_matchEvENKUlOT_E_clIRKNS_10observableIbNS3_13lift_operatorIbNSC_IN8pppppppp34ppppppppppppppppppppppppppppppppppENS3_6concatINSB_ISE_NS_18dynamic_observableISE_EEEENSB_ISI_NSG_ISI_EEEENS_19identity_one_workerEEENS3_22distinct_until_changedISE_NS_4util8equal_toIvEEEEEENS3_3mapISE_ZZNS6_18ppppppppppppppppppESE_ENKUlS8_E_clIRKNSB_ISE_SS_EEEEDaS8_EUlS7_E_EEEEEEEESZ_S8_EUlS7_E_E15filter_observerINS0_IbNS1_IbNST_IbZZNS6_17require_one_matchEvENKSA_IS15_EESZ_S8_EUlS7_E0_E12map_observerINS0_INSt12experimental8optionalINS6_15pppppppppppppppEEENS1_IS1F_NS_6detail22stateless_observer_tagEZNKS3_4takeIS1F_NSB_IS1F_NSC_IS1F_NSC_IbS12_S17_EES1A_EEEEiE12on_subscribeINS0_IS1F_NS1_IS1F_vvvvEEEEEEvRKS7_EUlS1F_E_ZNKS1N_IS1P_EEvS1R_EUlSt13exception_ptrE_ZNKS1N_IS1P_EEvS1R_EUlvE_EEEEEEvvvEEEEEEvvvEEE12nextdetacherC2EPKS23_"
This has more to do with QtCreator not having lldb support with Android. On Android Studio, lldb has no problem demangling these symbols and running the debug session smoothly. Currently, the only way to debug our project in QtCreator is to `set demangle-style none` in gdb startup commands, which leaves us with mangled stack traces.
- relates to
-
QTCREATORBUG-23260 Using LLDB as backend for Android
-
- Closed
-