Wifi bug

[e9hack]

Am 27.09.2021 um 14:01 schrieb Felix Fietkau:
> Normally it should be active by default. Is CONFIG_KERNEL_ELF_CORE set
> in your .config?

It was not activated, but the output from gdb looks not so helpful:

hb at vbox-linux6:~/src/openwrt/LEDE/archer-C7-ath79-5.10.x-dsa/build_dir/target-mips_74kc_musl/netifd-2021-09-21-08e954e1> ../../../scripts/remote-gdb netifd.1632747166.9335.11.core netifd
Choose target:
   1) mips_74kc (musl )
GNU gdb (GDB) 10.1
Copyright (C) 2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "--host=x86_64-pc-linux-gnu --target=mips-openwrt-linux-musl".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
     <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from netifd...
[New LWP 9335]
Core was generated by `/sbin/netifd'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x77d79ed5 in ?? (warning: GDB can't find the start of the function at 0x77d79ed5.

     GDB is unable to find the start of the function at 0x77d79ed5
and thus can't determine the size of that function's stack frame.
This means that GDB may be unable to access that stack frame, or
the frames below it.
     This problem is most likely caused by an invalid program counter or
stack pointer.
     However, if you think GDB should simply search farther back
from 0x77d79ed5 for code which looks like the beginning of a
function, you can increase the range of the search using the `set
heuristic-fence-post' command.
)
(gdb)

Regards,
Hartmut