On Thu, Jul 14, 2005 at 12:29:55PM -0500, Curt Arnold wrote:
>
> The CVS HEAD requires 1.x versions of apr and apr-util, not 0.9.x. I
> had considered attempting to support both APR-0.9.x and APR-1.x, but
> it added much too much complication.
>
> I occasionally check x86_64 builds. I haven't checked it recently,
> but I don't know any problems.
Ok... Now I dont get either of the bugs but I still get a crash which
seems traced to log4cxx codes. The crash happens after main() returns so
it must be called from some destructor of some global variables. The
trace is:
#0 0x00002aaaac872d5f in memcpy () from /lib/tls/libc.so.6
No symbol table info available.
#1 0x00002aaaac533baf in std::basic_string<wchar_t,
std::char_traits<wchar_t>, std::allocator<wchar_t> >::_Rep::_M_clone ()
from //usr/lib/gcc/x86_64-pc-linux-gnu/3.4.3/libstdc++.so.6
No symbol table info available.
#2 0x00002aaaac533c5a in std::basic_string<wchar_t,
std::char_traits<wchar_t>, std::allocator<wchar_t> >::basic_string ()
from //usr/lib/gcc/x86_64-pc-linux-gnu/3.4.3/libstdc++.so.6
No symbol table info available.
#3 0x00002aaaab391244 in log4cxx::NDC::get () at ndc.cpp:99
stack = (
std::stack<log4cxx::NDC::DiagnosticContext,std::deque<log4cxx::NDC::DiagnosticContext,
std::allocator<log4cxx::NDC::DiagnosticContext> > > &) @0x0: Cannot
access memory at address 0x0
Hmmm, seems to be something related to a NULL address, what is that
stack and what should it do ? Or any other hints to further debug this
problem...
Thanks!
--
Mihai RUSU Email: [EMAIL PROTECTED]
GPG : http://dizzy.roedu.net/dizzy-gpg.txt WWW: http://dizzy.roedu.net
"Linux is obsolete" -- AST
