-
Notifications
You must be signed in to change notification settings - Fork 896
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
Segmentation faults due to libpcap? #358
Comments
Hi @Manouchehri . Actually if you read official Valgrind explanation for definitely lost here, it says:
So i don't think this caused a SigFault, but, looking at your Valgrind log, it seems that those leaks are caused by the If u have ideas, please, explain and we can discuss about it. |
The memory leak errors are because it segfaults, and doesn't clean up. It definitely crashes. 🙁 |
[dave@lake github-358]$ sudo gdb --args ndpiReader -s 10 -i ens192
Reading symbols from ndpiReader...(no debugging symbols found)...done.
(gdb) r
Starting program: /usr/bin/ndpiReader -s 10 -i ens192
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
-----------------------------------------------------------
* NOTE: This is demo app to show *some* nDPI features.
* In this demo we have implemented only some basic features
* just to show you what you can do with the library. Feel
* free to extend it and send us the patches for inclusion
------------------------------------------------------------
Using nDPI (1.8.0-dev-754-92b1b46) [1 thread(s)]
Capturing live traffic from device ens192...
Capturing traffic up to 10 seconds
[New Thread 0x7ffff5ac8700 (LWP 2401)]
Running thread 0...
Thread 2 "ndpiReader" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7ffff5ac8700 (LWP 2401)]
0x00000000004299f5 in ssl_mark_and_payload_search_for_other_protocols ()
(gdb) generate-core-file
warning: target file /proc/2397/cmdline contained unexpected null characters
Saved corefile core.2397 |
Thank you. I have to check ASAP. |
@kYroL01 Let me know if there's anything I can help with and/or if you have trouble reproducing it. Thanks! |
@Manouchehri For sure |
@Manouchehri Can you please check if something changed with latest two commits 2b0809f and 29cd6ef ? Thanks |
Looks great, thank you! [dave@lake nDPI-tests]$ sudo ndpiReader -s 10 -i ens192 -v 2
-----------------------------------------------------------
* NOTE: This is demo app to show *some* nDPI features.
* In this demo we have implemented only some basic features
* just to show you what you can do with the library. Feel
* free to extend it and send us the patches for inclusion
------------------------------------------------------------
Using nDPI (1.8.0-makepkg-767-2b0809f) [1 thread(s)]
Capturing live traffic from device ens192...
Capturing traffic up to 10 seconds
Running thread 0...
1 TCP 192.168.190.153:59656 <-> 172.217.8.174:443 [proto: 91.126/SSL.Google][6 pkts/4961 bytes][client: google.com][server: *.google.com]
2 UDP 192.168.190.2:53 <-> 192.168.190.153:60025 [proto: 5/DNS][1 pkts/113 bytes][Host: git.savannah.gnu.org]
3 TCP 192.168.190.153:57330 <-> 208.118.235.201:9418 [proto: 226/Git][4 pkts/298 bytes]
4 TCP 192.168.190.153:59660 <-> 172.217.8.174:443 [proto: 91.126/SSL.Google][6 pkts/4961 bytes][client: google.com][server: *.google.com]
5 UDP 192.168.190.2:53 <-> 192.168.190.153:42970 [proto: 5/DNS][1 pkts/103 bytes][Host: google.com]
6 TCP 192.168.190.153:59662 <-> 172.217.8.174:443 [proto: 91.126/SSL.Google][6 pkts/4960 bytes][client: google.com][server: *.google.com]
7 TCP 192.168.190.153:59664 <-> 172.217.8.174:443 [proto: 91.126/SSL.Google][6 pkts/4960 bytes][client: google.com][server: *.google.com]
8 TCP 192.168.190.153:59666 <-> 172.217.8.174:443 [proto: 91.126/SSL.Google][6 pkts/4959 bytes][client: google.com][server: *.google.com]
9 TCP 192.168.190.153:59668 <-> 172.217.8.174:443 [proto: 91.126/SSL.Google][6 pkts/4960 bytes][client: google.com][server: *.google.com]
10 TCP 192.168.190.153:59670 <-> 172.217.8.174:443 [proto: 91.126/SSL.Google][6 pkts/4961 bytes][client: google.com][server: *.google.com]
11 UDP 192.168.190.2:53 <-> 192.168.190.153:37695 [proto: 5/DNS][1 pkts/103 bytes][Host: google.com]
12 TCP 172.217.1.110:443 <-> 192.168.190.153:47714 [proto: 91.126/SSL.Google][6 pkts/4960 bytes][client: google.com][server: *.google.com]
nDPI Memory statistics:
nDPI Memory (once): 110.55 KB
Flow Memory (per flow): 1.95 KB
Actual Memory: 2.22 MB
Peak Memory: 2.22 MB
Traffic statistics:
Ethernet bytes: 65365005 (includes ethernet CRC/IFC/trailer)
Discarded bytes: 0
IP packets: 9742 of 9742 packets total
IP bytes: 65131197 (avg pkt size 6685 bytes)
Unique flows: 13
TCP Packets: 9717
UDP Packets: 6
VLAN Packets: 0
MPLS Packets: 0
PPPoE Packets: 0
Fragmented Packets: 0
Max Packet size: 64259
Packet Len < 64: 4546
Packet Len 64-128: 40
Packet Len 128-256: 10
Packet Len 256-1024: 49
Packet Len 1024-1500: 213
Packet Len > 1500: 4884
nDPI throughput: 1.02 K pps / 51.98 Mb/sec
Traffic throughput: 1.02 K pps / 51.98 Mb/sec
Traffic duration: 9.593 sec
Guessed flow protos: 0
Detected protocols:
DNS packets: 6 bytes: 620 flows: 3
Google packets: 171 bytes: 54520 flows: 9
Git packets: 9565 bytes: 65076057 flows: 1
Protocol statistics:
Acceptable 65131197 bytes
1 UDP 192.168.190.2:53 <-> 192.168.190.153:37695 [proto: 5/DNS][2 pkts/200 bytes][Host: google.com]
2 TCP 172.217.1.110:443 <-> 192.168.190.153:47714 [proto: 91.126/SSL.Google][19 pkts/6583 bytes][client: google.com][server: *.google.com]
3 TCP 192.168.190.153:59656 <-> 172.217.8.174:443 [proto: 91.126/SSL.Google][19 pkts/6580 bytes][client: google.com][server: *.google.com]
4 TCP 192.168.190.153:59660 <-> 172.217.8.174:443 [proto: 91.126/SSL.Google][19 pkts/6580 bytes][client: google.com][server: *.google.com]
5 TCP 192.168.190.153:59662 <-> 172.217.8.174:443 [proto: 91.126/SSL.Google][19 pkts/6583 bytes][client: google.com][server: *.google.com]
6 TCP 192.168.190.153:59664 <-> 172.217.8.174:443 [proto: 91.126/SSL.Google][19 pkts/6583 bytes][client: google.com][server: *.google.com]
7 TCP 192.168.190.153:59666 <-> 172.217.8.174:443 [proto: 91.126/SSL.Google][19 pkts/6582 bytes][client: google.com][server: *.google.com]
8 TCP 192.168.190.153:59668 <-> 172.217.8.174:443 [proto: 91.126/SSL.Google][19 pkts/6583 bytes][client: google.com][server: *.google.com]
9 TCP 192.168.190.153:59670 <-> 172.217.8.174:443 [proto: 91.126/SSL.Google][19 pkts/6584 bytes][client: google.com][server: *.google.com]
10 UDP 192.168.190.2:53 <-> 192.168.190.153:60025 [proto: 5/DNS][2 pkts/220 bytes][Host: git.savannah.gnu.org]
11 TCP 192.168.190.153:57330 <-> 208.118.235.201:9418 [proto: 226/Git][9565 pkts/65076057 bytes]
12 ICMP 8.8.8.8:0 <-> 192.168.190.153:0 [proto: 81.126/ICMP.Google][19 pkts/1862 bytes]
13 UDP 192.168.190.2:53 <-> 192.168.190.153:42970 [proto: 5/DNS][2 pkts/200 bytes][Host: google.com]
|
I'm glad of this! |
Seems like this might be related to #249. Happens after a couple seconds of web browsing.
The text was updated successfully, but these errors were encountered: