From dev-return-22879-apmail-apr-dev-archive=apr.apache.org@apr.apache.org Thu Feb 04 22:52:29 2010 Return-Path: Delivered-To: apmail-apr-dev-archive@www.apache.org Received: (qmail 42699 invoked from network); 4 Feb 2010 22:52:29 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 4 Feb 2010 22:52:29 -0000 Received: (qmail 19344 invoked by uid 500); 4 Feb 2010 22:52:28 -0000 Delivered-To: apmail-apr-dev-archive@apr.apache.org Received: (qmail 19251 invoked by uid 500); 4 Feb 2010 22:52:28 -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 19243 invoked by uid 99); 4 Feb 2010 22:52:28 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 04 Feb 2010 22:52:28 +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 (athena.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; Thu, 04 Feb 2010 22:52:21 +0000 Received: from [10.1.120.24] (shrek.rexursive.com [10.1.120.24]) by beauty.rexursive.com (Postfix) with ESMTP id 846648D53C; Fri, 5 Feb 2010 09:51:59 +1100 (EST) Subject: Re: dbd p[v]b functions problem From: Bojan Smojver To: Bob Rossi Cc: dev@apr.apache.org In-Reply-To: <20100204224416.GA20966@brasko.net> References: <20100204224416.GA20966@brasko.net> Content-Type: text/plain; charset="UTF-8" Date: Fri, 05 Feb 2010 09:51:59 +1100 Message-ID: <1265323919.1858.3.camel@shrek.rexursive.com> Mime-Version: 1.0 X-Mailer: Evolution 2.28.2 (2.28.2-1.fc12) Content-Transfer-Encoding: 7bit On Thu, 2010-02-04 at 17:44 -0500, Bob Rossi wrote: > Is this a design decision or a flaw? Design decision. Just to be clear, you are getting segfaults when you are NOT passing pointers in, correct? If you are doing that, you are misusing the API and causing the segfaults. -- Bojan