Juergen Spitzmueller wrote:
Just to be sure: this is the segfault your recent patch fixes?
That one turned out to be a mirage. I'm not sure what was causing it,
but it was local to my machine. Probably some old libraries lying around
or something. There was another that was in 1.6.svn, but A
Just to be sure: this is the segfault your recent patch fixes?
Jürgen
Andre Poenitz wrote:
On Tue, Oct 02, 2007 at 03:48:51PM -0400, Richard Heck wrote:
Andre Poenitz wrote:
On Tue, Oct 02, 2007 at 03:33:39PM -0400, Richard Heck wrote:
#0 0x0865ea13 in boost::signals::connection::reset (this=0x99eee14,
new_con=0x9a116d0) at
../../../../boost/b
On Tue, Oct 02, 2007 at 03:48:51PM -0400, Richard Heck wrote:
> Andre Poenitz wrote:
> >On Tue, Oct 02, 2007 at 03:33:39PM -0400, Richard Heck wrote:
> >
> >>#0 0x0865ea13 in boost::signals::connection::reset (this=0x99eee14,
> >>new_con=0x9a116d0) at
> >>../../../../boost/boost/detail/sp_coun
Andre Poenitz wrote:
On Tue, Oct 02, 2007 at 03:33:39PM -0400, Richard Heck wrote:
#0 0x0865ea13 in boost::signals::connection::reset (this=0x99eee14,
new_con=0x9a116d0) at
../../../../boost/boost/detail/sp_counted_base_gcc_x86.hpp:50
When doing what?
It was just segfaulting on st
On Tue, Oct 02, 2007 at 03:33:39PM -0400, Richard Heck wrote:
>
> #0 0x0865ea13 in boost::signals::connection::reset (this=0x99eee14,
> new_con=0x9a116d0) at
> ../../../../boost/boost/detail/sp_counted_base_gcc_x86.hpp:50
> #1 0x08674a1b in boost::signals::detail::slot_base::create_connection
#0 0x0865ea13 in boost::signals::connection::reset (this=0x99eee14,
new_con=0x9a116d0) at
../../../../boost/boost/detail/sp_counted_base_gcc_x86.hpp:50
#1 0x08674a1b in boost::signals::detail::slot_base::create_connection
(this=0xbf8aa51c) at slot.cpp:33
#2 0x083c5813 in boost::slotstd::all
