Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ndpiReader 1.8.0 or ntopng 2.4 crashes while loading protos.txt #219

Closed
jjdevx opened this issue Jun 29, 2016 · 2 comments
Closed

ndpiReader 1.8.0 or ntopng 2.4 crashes while loading protos.txt #219

jjdevx opened this issue Jun 29, 2016 · 2 comments
Labels

Comments

@jjdevx
Copy link

jjdevx commented Jun 29, 2016

No matter which protocol is defined, it always crashes when it load the first protocol.
Trace from ndpiReader
Program terminated with signal 11, Segmentation fault.
#0 0x00007feb3a686645 in __strcasecmp_l_sse42 () from /lib64/libc.so.6

Missing separate debuginfos, use: debuginfo-install glibc-2.12-1.192.el6.x86_64 pfring-6.4.1-694.x86_64
(gdb) bt
#0 0x00007feb3a686645 in __strcasecmp_l_sse42 () from /lib64/libc.so.6
#1 0x000000000040cef1 in ndpi_handle_rule (ndpi_mod=0x1d05dd0, rule=0x7ffc70c7ffe0 "tcp:860,udp:860,tcp:3260,udp:3260", do_add=1 '\001') at ndpi_main.c:1969
#2 0x000000000040d3c4 in ndpi_load_protocols_file (ndpi_mod=0x1d05dd0, path=0x7ffc70c80877 "protos.txt") at ndpi_main.c:2076
#3 0x0000000000404486 in setupDetection (thread_id=0, pcap_handle=0x1d05070) at ndpiReader.c:647
#4 0x00000000004063d5 in test_lib () at ndpiReader.c:1249
#5 0x00000000004068ca in main (argc=, argv=) at ndpiReader.c:1317

(gdb) info threads

  • 1 Thread 0x7feb3d24e700 (LWP 30294) 0x00007feb3a686645 in __strcasecmp_l_sse42 () from /lib64/libc.so.6

ntopng is crashing with the same error when I enable nDPI protocols.

@kYroL01
Copy link
Contributor

kYroL01 commented Jun 29, 2016

The error is inside the ndpi_handle_rule function, when is called strcasecmp.
Have to check. Thanks for reporting.

@kYroL01 kYroL01 added the bug label Jul 1, 2016
@lucaderi
Copy link
Member

This bug cannot be reproduced and for me it works

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants