On Thu, 16 Oct 2008, Brian J. Murrell wrote: > OK. Figured out how to use ksymoops with the openwrt kernel build to > get a useful stack trace: > > $ ksymoops -v build_dir/linux-brcm47xx/linux-2.6.25.7/vmlinux -m > build_dir/linux-brcm47xx/linux-2.6.25.7/System.map > ksymoops 2.4.11 on i686 2.6.27-6-generic. Options used > -v build_dir/linux-brcm47xx/linux-2.6.25.7/vmlinux (specified) > -k /proc/ksyms (default) > -l /proc/modules (default) > -o /lib/modules/2.6.27-6-generic/ (default) > -m build_dir/linux-brcm47xx/linux-2.6.25.7/System.map (specified)
[...snip...] > Code; 80116358 <ioread8+8/c> > 8: ff 00 incl (%eax) > Code; 8011635a <ioread8+a/c> > a: 42 inc %edx > Code; 8011635b <ioread8+b/c> <===== > b: 30 00 xor %al,(%eax) <===== > Code; 8011635d <ioread16+1/c> > d: 00 82 94 08 00 e0 add %al,-0x1ffff76c(%edx) > Code; 80116363 <ioread16+7/c> > > I didn't mention before but this is running on an asus wl500gp FWIW. > This is not an instruction decode for the MIPS architecture. You need to use the -a switch to ksymoops, which probably means you need to compile a cross-tools version that is linked against a libbfd that understands the MIPS architecture. _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
