Bug#463929: exim4: Segfaults after libpq5 upgrade

[Jonathan McDowell]

On Mon, Feb 04, 2008 at 01:42:20PM +0100, Marc Haber wrote:
> On Mon, Feb 04, 2008 at 09:33:28AM +0000, Jonathan McDowell wrote:
> > After upgrading libpq5 from 8.2.6-1 to 8.3~rc2-1+b1 last night I
> > started to experience exim4 segfaults; log entries like:
> > 
> > 2008-02-03 23:51:21 1JLocK-0000PR-OM appendfile transport process
> > returned non-zero status 0x000b: terminated by signal 11
> 
> Any chance for a backtrace?

There's a limit to what I can do as it involves breaking mail for
people. Also it appears installing exim4-dbg forces eximon4 to be
installed, which then drags in X11 libraries. Meh.

limegreen:~# gdb mailq
GNU gdb 6.6.90.20070912-debian
Copyright (C) 2007 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu"...
(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(gdb) run
Starting program: /usr/bin/mailq 
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
---Type <return> to continue, or q <return> to quit---
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[New Thread 0x2ba2de5c6cc0 (LWP 2944)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x2ba2de5c6cc0 (LWP 2944)]
0x00002ba2dc19eb6b in free () from /lib/libc.so.6
(gdb) bt
#0  0x00002ba2dc19eb6b in free () from /lib/libc.so.6
#1  0x00002ba2dd5eee20 in ldap_int_destroy_global_options () at init.c:457
#2  0x00002ba2dd5d4512 in __do_global_dtors_aux ()
   from /usr/lib/libldap_r-2.4.so.2
#3  0x00007fffd120ba40 in ?? ()
#4  0x00002ba2dd5fc091 in _fini () from /usr/lib/libldap_r-2.4.so.2
#5  0x0000000000000000 in ?? ()

(that's with exim4-dbg and libldap-2.4-2-dbg installed)

> Greetings
> Marc, guessing that this is a libpq issue

Probably; the box doesn't do a lot else so I haven't noticed other
issues.

J.

-- 
Life's dangerous enough without mines in the garden.
This .sig brought to you by the letter O and the number  6
Product of the Republic of HuggieTag