Openwrt crash, how to build debuginfo to mt7628.ko?

[hnyman]

@cppcoffee

I use gdb to check it, and gdb says no debug symbols, how can I compile mt7628.ko with debug symbols

$ gdb ./build_dir/target-mipsel_24kec+dsp_uClibc-1.0.x/linux-ramips_mt7628/mt7628-4.1.1.0/ipkg-mipsel_24kec_dsp/kmod-mt7628/lib/modules/4.4.296/mt7628.ko

Although it may not help here (with vendor SDK), but for future use with the actual OpenWrt:

• build_dir contains the stripped versions without debug symbols
• staging_dir contains the original intermediate versions with debug symbols, before stripping.

You should provide the staging_dir path for gdb for debugging.

Example discussion e.g. in

Mt76 wireless driver debugging

A few hopefully helpful items for you: by default the final binaries in build_dir/ are stripped (debug info removed...), so you might need to provide gbb with the unstripped binaries from your staging_dir/ Like I do here: Nslookup ipv6 in lede 17.01.1 (fix: update busybox to 1.25.1-4) - #17 by hnyman you might also need to provide the default library path with set solib-search-path like this: set solib-search-path ./staging_dir/target-arm_cortex-a15+neon-vfpv4_musl_eabi/usr/lib/ (Exam…

Zerotier segmentation fault on upgrade

Note that the build_dir contains stripped binaries, while the staging_dir contains the originals before stripping. I have remote debugging in several ways: providing directly the unstripped binary: ./scripts/remote-gdb 192.168.1.2:9000 staging_dir/target-mips_34kc_musl-1.1.10/root-ar71xx/usr/sbin/collectd debugging a crash core file: ulimit -c unlimited in router, to make sure that cores can be stored Analysing the core, once it is transferred to the buildhost ./build_dir/toolchain…

• http://lists.openwrt.org/pipermail/openwrt-devel/2021-September/036506.html