Re: [arm-gnu] fatal error in "row_insert": std::runtime_error: Failure to bind on bulk operations, works on x86 windows and linux
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [arm-gnu] fatal error in "row_insert": std::runtime_error: Failure to bind on bulk operations, works on x86 windows and linux
- To: arm-gnu@xxxxxxxxxxxxxxxx
- Subject: Re: [arm-gnu] fatal error in "row_insert": std::runtime_error: Failure to bind on bulk operations, works on x86 windows and linux
- From: Christian Auby <christian@xxxxxxx>
- Date: Wed, 10 Feb 2010 16:21:59 +0100
How would I debug a program with no debug info? I'm also a bit muffed
why it works perfectly fine on other architectures.
regards,
Christian
On 2/10/2010 4:11 PM, Carlos O'Donell wrote:
> Christian Auby wrote:
>> I'm cross compiling SOCI (a C++ database lib) for ARM, using
>> CodeSourcery GCC version 4.4.1.
>>
>> I've written a small Boost unit test suite for SOCI, which can be seen
>> here:
>>
>> http://pastebin.ca/1792493
>>
>> The unit tests run successfully in the debug build, but crashes in the
>> release build with the following text:
>>
>> http://pastebin.ca/1792497
>>
>> Program received signal SIGSEGV, Segmentation fault.
>> in std::operator+<char, std::char_traits<char>, std::allocator<char> > ()
>>
>> I'm not entirely sure if this issue lies in SOCI or in the libs that
>> ship with CodeSourcery, so if anyone can shine any light on that I'd
>> appreciate it.
>
> This looks like an application issue (you have two "fatal errors"
> printed before the C library backtrace). It appears that the application
> called free with an invalid pointer and the C library was checking
> pointers. You will have to debug this with the CodeSourcery
> gdbserver/gdb and determine the cause of the failure.
>
> Good luck with your debugging.
>
> Cheers,
> Carlos.