Bug#662662: php5-memcached: Segfault or abort when getServerByKey, get called

Package: php5-memcached Version: 1.0.2-1 Severity: important Tags: upstream Calls to getServerByKey can cause a segfault or abort when followed by any other call that will read or write with the same key, or any key that happens to live on the same server. The bug is caused by a call to free the

Bug#629896: segfault while simply get()ing a value from squeeze memcached

You're quite right, I mistakenly sent this as a php-memcache bug. I'll submit it separately as a php-memcached bug. I'm hoping they will consider it serious, but we'll see. Thanks. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Co

Bug#629896: segfault while simply get()ing a value from squeeze memcached

I'm not sure if this is related, but I found a similar problem. We've also extended the memcached class with wrappers. We're getting segfaults after the get call in some cases, double-frees and aborts in other cases. However, the problem does not appear to be triggered by the get call itself. Addit

Bug#646036: pmake: mkdep does not exit if cc returns error

Package: pmake Version: 1.111-2+squeeze1 Severity: important mkdep ignores the return value of cc, so errors in cc do not propagate back up to the caller. The if [ $? != 0 ] test applies to the sed, which will probably never fail. The fix is probably to change the script so it writes to a temp