On 1/4/07, Shaun Jackman <[EMAIL PROTECTED]> wrote:
On 1/4/07, Zack Weinberg <[EMAIL PROTECTED]> wrote:
> Thanks for the symbol-ful backtrace. I regret to say I don't know
> what is going on there, but I have this bad feeling it's a Boost bug.
I get the same impression. Or, perhaps a difference
Thanks for the symbol-ful backtrace. I regret to say I don't know
what is going on there, but I have this bad feeling it's a Boost bug.
zw
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On 1/4/07, Zack Weinberg <[EMAIL PROTECTED]> wrote:
Thanks for the symbol-ful backtrace. I regret to say I don't know
what is going on there, but I have this bad feeling it's a Boost bug.
I get the same impression. Or, perhaps a difference between how Boost
was compiled for Debian and how mono
> "Brian" == Brian May <[EMAIL PROTECTED]> writes:
Brian> with debugging:
Please see:
http://bugs.debian.org/404616
as my mailing list post was blocked by the moderator for unknown
reasons.
(assuming this post makes it...)
--
Brian May <[EMAIL PROTECTED]>
--
To UNSUBSCRIBE, email t
On 12/31/06, Brian May <[EMAIL PROTECTED]> wrote:
Zack> 2) Run the crashing command under valgrind - valgrind does support PPC
Zack> now, I believe - and get us a backtrace from that.
==6046== Memcheck, a memory error detector.
==6046== Copyright (C) 2002-2006, and GNU GPL'd, by Julian Sew
> "Zack" == Zack Weinberg <[EMAIL PROTECTED]> writes:
Zack> 1) Make absolutely sure that the Boost libraries are compiled with the
Zack> same version of GCC as Monotone itself. This is the #1 cause of
Zack> inexplicable segfaults.
Build log of boost libraries:
http://buildd.debi
(gdb) bt
#0 0x0fe35ecc in __dynamic_cast () from /usr/lib/libstdc++.so.6
#1 0x100c1ef0 in std::out_of_range::~out_of_range ()
#2 0x10209214 in boost::detail::shared_count::~shared_count ()
#3 0x1012a674 in boost::gregorian::bad_month::~bad_month ()
#4 0x1012b060 in boost::gregorian::bad_month
7 matches
Mail list logo
