Skip to content

Memory sanitizer fires on snort #3

@mike-at-trout-software

Description

@mike-at-trout-software

The memory sanitizer fires when we run snort (at least with the test scripts), it also does this when run without any of our own inspectors.

This can either happen as a total failure in running:

.../inspectors/dhcp_monitor$ make
sh3 -o dhcp_monitor.so -i inspector.cc 
---- TEST_dhcp> pcap $moddir/pcaps/dhcp_clean.pcap
[stderr]
AddressSanitizer:DEADLYSIGNAL
AddressSanitizer:DEADLYSIGNAL
AddressSanitizer:DEADLYSIGNAL
AddressSanitizer:DEADLYSIGNAL
AddressSanitizer:DEADLYSIGNAL
AddressSanitizer:DEADLYSIGNAL
Test Failure: tests/dhcp.script:1: pcap /home/mike/code/snort/snort-extra/inspectors/dhcp_monitor/pcaps/dhcp_clean.pcap: signal: segmentation fault (core dumped)

Or as a reported error:

...

=================================================================
==31132==ERROR: LeakSanitizer: detected memory leaks

Direct leak of 8 byte(s) in 1 object(s) allocated from:
    #0 0x7cf5832b61e7 in operator new(unsigned long) ../../../../src/libsanitizer/asan/asan_new_delete.cpp:99
    #1 0x7cf581e2ee51 in InitModule src/malloc_extension.cc:212
    #2 0x7cf581e2ee51 in InitModule src/malloc_extension.cc:208
    #3 0x7cf581e2ee51 in MallocExtension::Register(MallocExtension*) src/malloc_extension.cc:226

SUMMARY: AddressSanitizer: 8 byte(s) leaked in 1 allocation(s).

...

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions