Thanks, I'll check it out. Can we have find some reference which packet make coredump For example Packet 1 make coredump I want find that packet by tcpdump and tell them do not send that packet to nfdump
MyWebSite http://mfaridi.com On Sat, 31 Oct 2020, 15:45 Brian Candler, <b.cand...@pobox.com> wrote: > On 31/10/2020 11:58, Mostaf Faridi wrote: > > Thank you for the clarification. > > How I undrestand which netflow make this error? > > By debugging the C code. > > Of course, the problem may have been fixed already, so before wasting > your time, you should first build nfcapd and nfdump from git HEAD and > see if the problem remains. > > Here are some of the many commits since 1.6.16 which might have fixed > your problem: > > commit c2a976e738fa1bf8d140bdd0cc45685b880dd63d > Author: Peter Haag <pe...@people.ops-trust.net> > Date: Fri Nov 8 07:34:55 2019 +0100 > > Fix corrupt file handling #193 > > commit 7bd6d5b81f68224d23c1df3dff066e35b20fae6c > Author: Peter Haag <pe...@people.ops-trust.net> > Date: Mon Aug 5 09:39:01 2019 +0200 > > Fix off by 1 array. #173 > > commit 9f0fe9563366f62a71d34c92229da3432ec5cf0e > Author: Peter Haag <pe...@people.ops-trust.net> > Date: Sun Apr 1 10:30:25 2018 +0200 > > Fix nfdump crashes, when feeded with garbage input. Issue #104 > > commit b776f8df7028059863b1e89cd8f52f2afaebbdc8 > Author: Peter Haag <peter@Pegasus.local> > Date: Thu Dec 21 17:21:44 2017 +0100 > > Fix wrong offset calculation if unknown options are found > > For the last of those commits, there are more details in issue #77: > https://github.com/phaag/nfdump/issues/77 > > If the problem still exists in current code, then you should find a C > programmer who knows how to drive gdb to help you with the debugging. > > Regards, > > Brian. > >
_______________________________________________ Nfdump-discuss mailing list Nfdump-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfdump-discuss
