Return-Path: Delivered-To: apmail-apr-dev-archive@www.apache.org Received: (qmail 57267 invoked from network); 27 Jan 2010 05:50:07 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 27 Jan 2010 05:50:07 -0000 Received: (qmail 82419 invoked by uid 500); 27 Jan 2010 05:50:07 -0000 Delivered-To: apmail-apr-dev-archive@apr.apache.org Received: (qmail 82136 invoked by uid 500); 27 Jan 2010 05:50:07 -0000 Mailing-List: contact dev-help@apr.apache.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Id: Delivered-To: mailing list dev@apr.apache.org Received: (qmail 82128 invoked by uid 99); 27 Jan 2010 05:50:06 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 Jan 2010 05:50:06 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of bojan@rexursive.com designates 150.101.121.179 as permitted sender) Received: from [150.101.121.179] (HELO beauty.rexursive.com) (150.101.121.179) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 Jan 2010 05:49:58 +0000 Received: from [10.1.120.24] (shrek.rexursive.com [10.1.120.24]) by beauty.rexursive.com (Postfix) with ESMTP id 8A7B08C382; Wed, 27 Jan 2010 16:49:35 +1100 (EST) Subject: Re: About DBD Prepare Statement Problem From: Bojan Smojver To: liuxulin Cc: dev@apr.apache.org In-Reply-To: <4B5FD1B6.5090905@gmail.com> References: <4B5FD1B6.5090905@gmail.com> Content-Type: text/plain; charset="UTF-8" Date: Wed, 27 Jan 2010 16:49:35 +1100 Message-ID: <1264571375.2527.2.camel@shrek.rexursive.com> Mime-Version: 1.0 X-Mailer: Evolution 2.28.2 (2.28.2-1.fc12) Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org On Wed, 2010-01-27 at 13:40 +0800, liuxulin wrote: > Is there anything wrong? Without going into details, compile the thing (your program and APU) with -g and -O0, then run it with gdb and step all the way through to see where the failure actually occurs. This will give you a better indication as to what actually went wrong. Also, increase verbosity of you MySQL log, in order to see what's going on on the server side. -- Bojan