dansguardian doesn't start anymore since upgrade to macports 2.1.0

[fclaire@…]

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 ?

[ryandesign (Ryan Carsten Schmidt)]

Since we have no maintainer for this port in MacPorts, I suggest you work directly with the developer(s) of the software to resolve the issue.

[fclaire@…]

I've posted a message on the dansguardian mailing list but this open-source project isn't actively supported anymore. Could you give me some hints on what changed between 2.0.4 and 2.1.0 ? Has the default C++ compiler changed ?

I'm not a C++ developer and I don't have a clue why this init call fails like that. Is there any experienced C++ guy around within the macports maintainers ?

[ryandesign (Ryan Carsten Schmidt)]

To my knowledge nothing that changed between MacPorts 2.0 and 2.1 should affect the functioning of your ports. The default compiler is based on the Xcode version.

[fclaire@…]

I rolled back my entire /opt/local directory from a time machine backup to what it was 6 days ago. It put back macports 2.0.4 and a working copy of dansguardian.

This solved my problem and I won't do selfupdate anymore.

[bitpup]

Cc Me!

[l.laspada@…]

Cc Me!