On Thu, Nov 19, 2009 at 10:57 PM, Shawn Yarbrough <[email protected]> wrote: > #0 0x00007f8edfcfffb5 in raise () from /lib/libc.so.6 > #1 0x00007f8edfd01bc3 in abort () from /lib/libc.so.6 > #2 0x00007f8edfcf8f09 in __assert_fail () from /lib/libc.so.6 > #3 0x00007f8ee0cf9c3c in Handler (this=0x7f8ed41628f0, session=<value > optimized out>, request=<value optimized out>) at > /usr/include/boost/thread/pthread/mutex.hpp:50 > #4 0x00007f8ee0bb8538 in UpdateLock (this=0x7f8ebefec690, a...@0x2512f80) > at /build/buildd/witty-2.2.4/src/Wt/WApplication.C:898 > #5 0x00007f8ee0bb85b9 in Wt::WApplication::getUpdateLock (this=0xc9c) at > /build/buildd/witty-2.2.4/src/Wt/WApplication.C:889 > > Frame #6 is my code, the line where I call "Wt::WApplication::UpdateLock > lock = app->getUpdateLock();" from a thread. This is with Ubuntu Linux and > the dedicated Wt web server. > > Any ideas what is going wrong here? I haven't tried to track down line 898 > yet, because the debugger isn't showing it to me.
What version of Ubuntu and the witty Ubuntu packages is that? What version of libc6? Have you tried installing witty-dbg and starting with LD_LIBRARY_PATH set to /usr/lib/debug/usr/lib:$LD_LIBRARY_PATH? (that'll run the app against the debug version of the Wt libraries) There are some memory management issues in old glibc versions (the one in Hardy, for instance), we hit that in KDE too. -- Pau Garcia i Quiles http://www.elpauer.org (Due to my workload, I may need 10 days to answer) ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ witty-interest mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/witty-interest
