Hi, Glenn, I don't know if this is practical, but you could build tcpborphserver3 with debugging enabled (-g compiler option) and then run tcpborphserver under gdb in a screen session of the roach. When/if it crashes you can go to the gdb session to see exactly where/why it crashed.
Dave On Jan 17, 2013, at 8:38 AM, G Jones wrote: > Hi, > We have been running eight ROACH IIs for the past few weeks using > tcpborphserver3 and have experienced occasional "crashes" where the > ROACH stops responding to KATCP and upon investigation we find that > the tcpborphserver3 program is no longer running. > > uname -a gives > Linux vegasr2-3 3.7.0-rc2+ #20 Fri Jan 4 18:04:26 SAST 2013 ppc GNU/Linux > > and tcpborphserver3 is a clean compile from git, compiled on the ROACH itself. > > I see that tcpborphserver3 looks like it has some debugging/logging > features which are disabled by default. Can anyone recommend how to > best enable them to track this down, especially in light of having the > filesystems network mounted and read-only? > > Thanks, > Glenn >
