opensubscriber
   Find in this group all groups
 
Unknown more information…

b : binc@bincimap.org 12 September 2005 • 9:41PM -0400

Re: [binc] problem with 1.2.13 (freebsd port) - core dumped on signal 10
by Peter Stuge

REPLY TO AUTHOR
 
REPLY TO GROUP




On Mon, Sep 12, 2005 at 03:22:49PM +0200, Andrea Riela wrote:
> Core was generated by `bincimap-up'.
> Program terminated with signal 10, Bus error.
[..]
> #0  0x080661da in std::operator+<char, std::char_traits<char>,
> std::allocator<char> > ()

There we go.

bincimap-up crashed while inside the standard C++ library, it seems
to have been when trying to append a character to a string, but
others more familiar with the library will make more of it.


> (gdb) bt
> #0  0x080661da in std::operator+<char, std::char_traits<char>,
> std::allocator<char> > ()
> #1  0x08065d47 in std::operator+<char, std::char_traits<char>,
> std::allocator<char> > ()
> #2  0x08069ced in __gnu_cxx::new_allocator<char>::deallocate ()
> #3  0x08065984 in std::operator+<char, std::char_traits<char>,
> std::allocator<char> > ()
> #4  0x08065328 in std::operator+<char, std::char_traits<char>,
> std::allocator<char> > ()
> #5  0x08074da2 in __gnu_cxx::new_allocator<char>::deallocate ()
> #6  0x08074e52 in __gnu_cxx::new_allocator<char>::deallocate ()
> #7  0x0805d3b1 in std::operator+<char, std::char_traits<char>,
> std::allocator<char> > ()
> #8  0x0805a2cf in std::operator+<char, std::char_traits<char>,
> std::allocator<char> > ()
> #9  0x0804a969 in ?? ()
> #10 0x00000007 in ?? ()
> #11 0xbfbfeb90 in ?? ()
> #12 0xbfbfebb0 in ?? ()
> #13 0x0804a95e in ?? ()
> #14 0x0808af34 in std::operator==<char, std::char_traits<char>,
> std::allocator<char> > ()
> #15 0x00000007 in ?? ()

Lots of steps inside the library.

Which version of libc are you using? Is it glibc?


//Peter

Bookmark with:

Delicious   Digg   reddit   Facebook   StumbleUpon

Related Messages

opensubscriber is not affiliated with the authors of this message nor responsible for its content.