DBMail (I tried versions from 2.2.9 and 2.2.17) emerged with use flags: ldap postgres python sieve.
All DBmail executables hands on exit with message:
*** glibc detected *** dbmail-util: free(): invalid pointer: 0xXXXXXXXX ***
For example dbmail-util -cpdy
In case of create /etc/portage/bashrc (according to http://en.gentoo-wiki.com/wiki/Safe_LDFLAGS) and set:
in package.ldflags, DBMail runs fine without errors.
Steps to Reproduce:
1. Set net-mail/dbmail use flags: ldap postgres python sieve
2. emerge dbmail
3. Configure dbmail with postgresql
4. dbmail-util -cpdy
Default LDFLAGS in /usr/portage/profiles/default/linux/make.defaults is LDFLAGS="-Wl,-O1 -Wl,--as-needed"
I don't know how to define separate LDFLAGS for ebuild without /etc/portage/bashrc and /etc/portage/package.ldflags
please post `emerge --info` in every bug report. also, post the full build log as an attachment.
Created attachment 269195 [details]
net-mail/dbmail-2.2.17 build log
Created attachment 269199 [details]
Created attachment 269201 [details]
net-mail/dbmail-2.2.17 build log, with LDFLAGS unset
Created attachment 269203 [details]
Not only dbmail-utils crashed on exit! I tried also other executables with the same result: dbmail-imapd, dbmail-pop3 and dbmail-smtp.
odd I have the same useflags - and use it with postgresql - apart from ldap.
which postgresql (-base, -server, libpq) do you have?
-server, but of course, -base also installed.
Latest version installed: 9.0.4-r2
Latest version installed: 9.0.4-r1
Don't forget. I also use CPU specific GCC flags:
CFLAGS="-O2 -march=k8-sse3 -pipe -fomit-frame-pointer -mmmx -msse2 -mfpmath=sse -msse3 -m3dnow"
postgresql-server 8.3.12 .
CFLAGS="-march=athlon64 -O2 -pipe"
In any case it seems to be a problem with some of your CFLAGS.
Could you do some experiments which ones cause the problem? because then
1) you can report to upstream about it
2) we can use flag-o-matic.eclass to replace/remove one/some flags
Did you try version 3.0.2 (in my dev-overlay) yet?
-- If you don'T want to add my overlay, I will put it in the maintree today or the following days after checking out some libzdb issue
3.0.2 is in the official tree please test this