From: Warren Young
Date: June 25 2009 5:42am
Subject: Re: Core dumps even after using exceptions in connection object
List-Archive: http://lists.mysql.com/plusplus/8643
Message-Id: <0B1F7D29-3692-415D-B3BE-EDE7549CED58@etr-usa.com>
MIME-Version: 1.0 (Apple Message framework v935.3)
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit

On Jun 22, 2009, at 8:42 AM, Ankur Saxena wrote:

> #4  0x00e5db10 in Row (this=0x69ba6b0, d=@0x69ba60c, r=0x1,  
> jj=0x82c34ac) at
> /usr/include/c++/3.2.2/bits/stl_alloc.h:664
> 664     /usr/include/c++/3.2.2/bits/stl_alloc.h: No such file or  
> directory.
>        in /usr/include/c++/3.2.2/bits/stl_alloc.h
> (gdb)
> #5  0x08169f79 in mysqlpp::Result::fetch_row (this=0x69ba700) at
> /home/ankur/mysql-api/mysql++/include/noexceptions.h:72
> 72      /home/ankur/mysql-api/mysql++/include/noexceptions.h: No  
> such file
> or directory.
>        in /home/ankur/mysql-api/mysql++/include/noexceptions.h

These missing file warnings hint that you're not running this program  
on the same machine as you built it on.  If the other machine is  
different enough from the build machine, it can cause strange crashes  
due to ABI conflicts and such.

> #6  0x08169c18 in mysqlpp::Result::at (this=0x69ba700, i=0) at
> /home/ankur/mysql-api/mysql++/include/result.h:431

So...you're trying to access res[0] in your code.  Are you checking  
that the result set is not empty before indexing into it?