Well, this is useful because you have your FW build and your symbols right next to it for each build.
Then, you can store them somewhere (FW + debug symbols) and if you get a crash/segfault on a specific build number you're covered because you can pull symbols and use them on coredumps for that specific build. On 1 Aug 2014 14:34, "Karl P" <ka...@tweak.net.au> wrote: > > > On 08/01/2014 11:27 AM, Felix Fietkau wrote: > >> On 2014-07-24 17:26, Helmut Schaa wrote: >> >>> Introduce a new config symbol EXTRACT_DEBUGINFO to extract debuginfo >>> from all binaries. This depends on USE_STRIP and DEBUG. >>> >>> The debuginfo of all packages will be extracted from the binary >>> and copied into "bin/$platform/debuginfo". >>> >>> This allows better debugging of coredumps by loading the debuginfo >>> into gdb. >>> >>> Signed-off-by: Helmut Schaa <helmut.sc...@googlemail.com> >>> >> How does this patch help with debugging? Debug info is already staged in >> staging_dir/target-*/root-*. This path is used by scripts/remote-gdb, >> which also accepts corefiles. >> > > That sounds awesome. Maybe you could elaborate on this either here: > http://wiki.openwrt.org/doc/devel/debugging > or > http://wiki.openwrt.org/doc/devel/gdb > > There's clearly lots of useful stuff there that no-one else knows about. > > Cheers, > Karl P > _______________________________________________ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel >
_______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
