[Pkg-postgresql-public] Bug#742493: pgmemcache segfaults with libmemcached11

[Hannu Valtonen]

Hi,

This has now been fixed by: 
https://github.com/ohmu/pgmemcache/commit/47623a545be485d6dd1ffb917e990d267ad57f35

- Hannu


On 2.4.2014 19.02, Christoph Berg wrote:
> Hi,
>
> when rebuilt with libmemcached11, pgmemcache in Debian started to
> segfault. It worked with libmemcached10 before.
>
> I'm not sure whose fault this is - pgmemcache or libmemcached, or
> possibly both. Hannu, Michael, could you have a look at this?
>
> (Unforatunately I couldn't find an email for libmemcached, just the
> launchpad tracker.)
>
> ----- Forwarded message from Christoph Berg <christoph.berg at credativ.de> -----
>
> Date: Mon, 24 Mar 2014 13:32:05 +0100
> From: Christoph Berg <christoph.berg at credativ.de>
> Reply-To: Christoph Berg <christoph.berg at credativ.de>, 742493 at bugs.debian.org
> To: Debian Bug Tracking System <submit at bugs.debian.org>
> Subject: Bug#742493: Segfault with libmemcached11
> X-Debian-PR-Message: report 742493
> X-Debian-PR-Package: postgresql-9.3-pgmemcache
> X-Debian-PR-Keywords:
> X-Debian-PR-Source: pgmemcache
>
> Package: postgresql-9.3-pgmemcache
> Version: 2.1.2-1+b1
> Severity: grave
>
> The binnum to update the dependency from libmemcached10 to
> libmemcached11 seems to have broken the PostgreSQL module:
>
> http://ci.debian.net/data/unstable-amd64/packages/p/pgmemcache/2014-03-23.log
>
> Also in my chroot:
>
> test init                     ... ok
> test start_memcached          ... ok
> test test                     ... FAILED (test process exited with exit code 2)
> test stop_memcached           ... ok
>
> 2014-03-24 13:16:05 CET LOG:  Serverprozess (PID 25224) wurde von Signal 11 beendet: Segmentation fault
> 2014-03-24 13:16:05 CET DETAIL:  Der fehlgeschlagene Prozess führte aus: SELECT regexp_replace(memcache_stats(), 'pid:.*', '') AS memcache_stats;
> 2014-03-24 13:16:05 CET LOG:  aktive Serverprozesse werden abgebrochen
> 2014-03-24 13:16:05 CET WARNUNG:  breche Verbindung ab wegen Absturz eines anderen Serverprozesses
> 2014-03-24 13:16:05 CET DETAIL:  Der Postmaster hat diesen Serverprozess angewiesen, die aktuelle Transaktion zurückzurollen und die Sitzung zu beenden, weil ein anderer Serverprozess abnormal beendet wurde und möglicherweise das Shared Memory verfälscht hat.
>
> ! psql:test.sql:2: SSL SYSCALL error: EOF detected
> ! psql:test.sql:2: connection to server was lost
>
> Christoph