[MacPorts] #34548: dansguardian doesn't start anymore since upgrade to macports 2.1.0
MacPorts
noreply at macports.org
Sun May 20 22:01:32 PDT 2012
#34548: dansguardian doesn't start anymore since upgrade to macports 2.1.0
-----------------------------+----------------------------------------------
Reporter: fclaire@… | Owner: macports-tickets@…
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 2.1.1
Keywords: | Port: dansguardian
-----------------------------+----------------------------------------------
dansguardian crashes with a mad mmap size value error message when started
with default configuration files on a clean install:
{{{
$ dansguardian
dansguardian(63116) malloc: *** mmap(size=1125728108154880) failed (error
code=12)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
std::bad_alloc
Error parsing the dansguardian.conf file or other DansGuardian
configuration files
}}}
I could narrow down the problem coming from line
{{{
int rc = dmpp->init(&lastplugin);
}}}
in the file src/OptionContainer.cpp
Note this problem happens only with macports > 2.1.0. With 2.0.4
dansguardian starts well with the default config files.
I could reproduce the problem on both 10.6 and 10.7 machines and with
macport 2.1.0 and 2.1.1. Any idea why mmap() asks for this huge amount of
memory ?
--
Ticket URL: <https://trac.macports.org/ticket/34548>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list