X-Original-To: alpine-infra@alpinelinux.org Delivered-To: alpine-infra@mail.alpinelinux.org Received: from mail-tul01m020-f171.google.com (mail-tul01m020-f171.google.com [209.85.214.171]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by mail.alpinelinux.org (Postfix) with ESMTPS id 76FA0DC00C4; Wed, 11 Jan 2012 03:07:30 +0000 (UTC) Received: by obbwd20 with SMTP id wd20so1051810obb.30 for ; Tue, 10 Jan 2012 19:07:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=f9asbbHkJLpyWtGxB2xQMu0RpglEMZZtQwBlOf5uflk=; b=DugQA4ruKtZHGnY4aRQZdFayF+l31cs41RP1ee/veGfPfHHtcsYuzM2snt9j7Tif0A UJj41ynL3H7/JJT0SQh2vjzeOY0Wm/CL3t9sD6pWMJWCe2mjehOfyG7DzZAicy1pG94Y XcqHttgPJiVC5xa/qJ1Mt/a1jq/w0914iYA38= MIME-Version: 1.0 Received: by 10.182.109.106 with SMTP id hr10mr20865220obb.27.1326251249829; Tue, 10 Jan 2012 19:07:29 -0800 (PST) Received: by 10.182.14.3 with HTTP; Tue, 10 Jan 2012 19:07:29 -0800 (PST) In-Reply-To: <4F0CDBFB.8010707@nothome.org> References: <4F0C8B9E.40808@nothome.org> <2B149571-CAE6-463D-BDD7-EE2CA5B74977@gmail.com> <4F0CDBFB.8010707@nothome.org> Date: Tue, 10 Jan 2012 22:07:29 -0500 Message-ID: Subject: Re: Bugs.a.o From: Jeff Bilyk To: fabled@alpinelinux.org Cc: alpine-infra@alpinelinux.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On Tue, Jan 10, 2012 at 7:46 PM, Nathan Angelacos wrot= e: > On 01/10/2012 01:53 PM, Carlo Landmeter wrote: >> >> Also had issues with pg on uc. It's the price we pay off trying to be >> differed... >> >> On Jan 10, 2012 10:49 PM, "Jeff Bilyk" > > wrote: >> >> =A0 =A0Thanks. =A0I should be back home in a few hours, if you need a ha= nd, I >> =A0 =A0can give it a try. =A0Fwiw, Ubuntu's MySQL package doesn't suffer= the >> =A0 =A0same bug as far as we could tell. =A0Fabled figured it was someth= ing in >> =A0 =A0uclibc iirc that was causing this crash, but we weren't able to >> =A0 =A0isolate exactly what the bug was... >> > > This is good for tracking down the bug then... we have a repeatable > scenario. > > Fabled, any chance we could get a bit of your time tomorrow to try to track down this issue? It's the same bug you were helping me with earlier in the year (http://bugs.mysql.com/bug.php?id=3D62634). Unfortunately, upstream just keeps saying "can't replicate, try mysql $LATESTVER"... Jeff