Re: A difficult question about locale_mutex uninitialized

2006-09-07 Thread Benjamin Kosnik
(on-list reply to off-list followup, author stripped by request) > [Off list] > > Doesn't the compiler itself also have to be originally built with thread > support (one of the magic configure flags)? Yes. Many of the targets for gcc default to thread support, such as some of the BSD's and linu

Re: A difficult question about locale_mutex uninitialized

2006-09-07 Thread Benjamin Kosnik
> SEH: System call: ose_mutex_lock > SEH: Error: A pointer to an uninitialized mutex (at 0x00b27988) was presented > to > the kernSEH: Information about current process "core_supervisor" > SEH: Pid 0x0001000b bid 0x00010008 progpid 0x > SEH: Callstack backtrace: > SEH: FrameAddress Retur

A difficult question about locale_mutex uninitialized

2006-09-06 Thread FCG WANG Baohua
Dear All: We met a problem when using GCC libstdc++.a on PowerPC-OSE platform(it use cross-compile tool with GCC 3.4.1). When starting our application("core_supervisor"), the OSE operation system always outputs the following message: SEH: System call: ose_mutex_lock SEH: Error: A pointer to a