List:MySQL++« Previous MessageNext Message »
From:Jay Rajput Date:June 23 2009 7:27pm
Subject:Re: Core dumps even after using exceptions in connection object
View as plain text  
Hi Ankur,

Can you trying simulating the core dumps which you are seeing in a
small example. Or can you share the actual code that will help others
to find out where the problem is. You need to simplify the code so
that we can  understand it. Or you can try running valgrind or some
other memory detection tool on your code and see if it comes out with
something. Memory corruption can create weird problems.

You might be using the APIs in a way which might be wrong and somebody
in the list can tell that. Sure it will not be me, but there are
others who know much better than me.

Just my two cents.
Jay.

On Mon, Jun 22, 2009 at 10:42 AM, Ankur Saxena<ankur.saxena@stripped> wrote:
> Hi,
>
> I have a API that my application uses which intern uses mysql++ api.
>
> I keep getting core dumps at certain point where I have enclosed the code
> with try and catch. Makes no sense. Please help.
>
> Here is the output from gdb.
>
>
> #0  0x00ca19b2 in std::__default_alloc_template<true, 0>::allocate ()
> from
> /usr/lib/libstdc++.so.5
> (gdb) up
> #1  0x00ca7178 in std::string::_Rep::_S_create () from
> /usr/lib/libstdc++.so.5
> (gdb)
> #2  0x00ca7f7f in std::string::_M_replace_safe<char const*> () from
> /usr/lib/libstdc++.so.5
> (gdb)
> #3  0x00ca47b9 in std::basic_string<char, std::char_traits<char>,
> std::allocator<char> >::basic_string () from /usr/lib/libstdc++.so.5
> (gdb)
> #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
> (gdb)
> #6  0x08169c18 in mysqlpp::Result::at (this=0x69ba700, i=0) at
> /home/ankur/mysql-api/mysql++/include/result.h:431
> 431     /home/ankur/mysql-api/mysql++/include/result.h: No such file or
> directory.
>        in /home/ankur/mysql-api/mysql++/include/result.h
> (gdb)
> #7  0x0817f93f in DBAccess::getCallFwdData (this=0x8282f18, imsi=0xb3783ac8
> "334723120728090", state=6, profile=0xb3783208, Log=0x69baf90)
>    at /home/ankur/mysql-api/mysql++/include/resiter.h:181
> 181     /home/ankur/mysql-api/mysql++/include/resiter.h: No such file or
> directory.
>        in /home/ankur/mysql-api/mysql++/include/resiter.h
> (gdb)
> #8  0x0817f25a in DBAccess::getMSProfile (this=0x8282f18, imsi=0xb3783ac8
> "334723120728090", state=6, profile=0xb3783208, Log=0x69baf90) at
> Features.cpp:423
> 423     Features.cpp: No such file or directory.
>        in Features.cpp
> (gdb)
> #9  0x0816aaed in DBAccess::findNumber (this=0x8282f18, search_str=0x82c2d88
> "3120728090", field_type=2 '\002', equip_id=0x82c2da8 "", regMS=0xb37830ec,
>    run_mask=1 '\001', Log=0x69baf90) at FindNumber.cpp:142
> 142     FindNumber.cpp: No such file or directory.
>        in FindNumber.cpp
>
>
> Thanks
>
> Ankur
>
Thread
Core dumps even after using exceptions in connection objectAnkur Saxena22 Jun
  • Re: Core dumps even after using exceptions in connection objectJay Rajput23 Jun
  • Re: Core dumps even after using exceptions in connection objectWarren Young25 Jun