On 2016/12/13 12:23, Lars Noodén wrote:
> On a BeagleBone Black (one that has not been used for GPIO), I have
> been getting segfaults with tcpdump since the last four or so
> snapshots. Running tcpdump in any way triggers the fault.
A backtrace would be nice, or even better build with symbols and get
a backtrace from that.
if you don't have a full source checkout handy, you can just fetch tcpdump:
cd /usr; cvs get -P src/usr.sbin/tcpdump
then:
cd /usr/src/usr.sbin/tcpdump
make obj; make clean; make DEBUG=-g
gdb obj/tcpdump
run
bt
You can also do a date-based checkout ("cvs up -D 2016/11/23" etc) to narrow
down the commit that broke it.
