#17753: tcpdump do "Segmentation fault"
--------------------------+-----------------------------------
  Reporter:  dev@…        |      Owner:  developers
      Type:  defect       |     Status:  new
  Priority:  normal       |  Milestone:  Barrier Breaker 14.07
 Component:  base system  |    Version:  Trunk
Resolution:               |   Keywords:
--------------------------+-----------------------------------

Comment (by svpcom@…):

 Hi, I also got segfault for any libpcap related binaries (tcpdump, iftop,
 etc).
 System is a:
 DISTRIB_ID="OpenWrt"
 DISTRIB_RELEASE="14.07"
 DISTRIB_REVISION="r42625"
 DISTRIB_CODENAME="barrier_breaker"
 DISTRIB_TARGET="octeon/generic"
 DISTRIB_DESCRIPTION="OpenWrt Barrier Breaker 14.07"

 downloaded from openwrt site
 # cat /proc/version
 Linux version 3.10.49 (bb@builder1) (gcc version 4.6.4 (OpenWrt/Linaro GCC
 4.6-2013.05 r42625) ) #3 SMP Wed Oct 1 16:27:17 CEST 2014

 gdb output:
 -----
 # gdb tcpdump
 GNU gdb (GDB) 7.5
 Copyright (C) 2012 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 "mips64-openwrt-linux".
 For bug reporting instructions, please see:
 <http://www.gnu.org/software/gdb/bugs/>...
 Reading symbols from /usr/sbin/tcpdump...(no debugging symbols
 found)...done.
 (gdb) ru -i eth1
 Starting program: /usr/sbin/tcpdump -i eth1
 warning: no loadable sections found in added symbol-file
 /lib/ld64-uClibc.so.0
 warning: Unable to find dynamic linker breakpoint function.
 GDB will be unable to debug shared library initializers
 and track explicitly loaded dynamic code.

 Program received signal SIGSEGV, Segmentation fault.
 0x000000fff7faf004 in ?? ()
 (gdb) bt
 #0  0x000000fff7faf004 in ?? ()
 warning: GDB can't find the start of the function at 0xfff7faf004.

     GDB is unable to find the start of the function at 0xfff7faf004
 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 0xfff7faf004 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)
 -------

--
Ticket URL: <https://dev.openwrt.org/ticket/17753#comment:4>
OpenWrt <http://openwrt.org>
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
[email protected]
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-tickets

Reply via email to