[haiku-development] Re: 32bit-wchar_t branch has been merged into trunk - full rebuild necessary

  • From: Oliver Tappe <zooey@xxxxxxxxxxxxxxx>
  • To: haiku-development@xxxxxxxxxxxxx
  • Date: Wed, 08 Jul 2009 03:37:31 +0200

On 2009-07-08 at 02:44:43 [+0200], Ingo Weinhold <ingo_weinhold@xxxxxx> wrote:
> 
> -------- Original-Nachricht --------
> > Datum: Tue, 07 Jul 2009 12:36:57 +0200
> > Von: Oliver Tappe <zooey@xxxxxxxxxxxxxxx>
> 
> > I have just merged the work on wchar_t (and some more) into r31443 of the
> > trunk, as a
> > result you need to update to that or a later revision and then rebuild
> > everything,
> > i.e. the buildtools and haiku itself.
> > 
> > Please tell if you encounter any peculiarities.
> 
> I've tried building under gcc2, but gensyscallinfos reproducibly triggers an 
> assert in the allocator:
> 
> gensyscallinfos: 
> /home/bonefish/develop/haiku/haiku/src/system/libroot/posix/malloc/processheap
> .cpp:166:void BPrivate::processHeap::free(void *): sb
> 
> [Switching to team 
> /Transfer/haiku/generated-gcc2/objects/haiku_host/x86/release/t (5047) thread 
> gensyscallinfos (5047)]
> 0xffff0114 in ?? ()
> (gdb) bt
> #0  0xffff0114 in ?? ()
> #1  0x0027cb06 in debugger () from /boot/system/lib/libroot.so
> #2  0x00285f71 in __assert_fail () from /boot/system/lib/libroot.so
> #3  0x0028f79c in BPrivate::processHeap::free ()
>    from /boot/system/lib/libroot.so
> #4  0x00291061 in free () from /boot/system/lib/libroot.so
> #5  0x0027abe8 in __builtin_vec_delete () from /boot/system/lib/libroot.so
> #6  0x00239778 in ifstream::~ifstream () from /boot/system/lib/libstdc++.r4.so
> #7  0x0020b786 in Main::_ParseSyscalls ()
> #8  0x00206834 in main ()
> 
> IIRC you changed something in the STL stream headers. Does that ring a bell?

Hm, I changed the signature of stringsteam::setbuf() to match its base. While 
the crash that triggered me changing it looked a lot like the one above (only 
stringstream instead of fstream), the fstream.h header does have the right 
signature in setbuf(), though.

So: nope, no bell ringing.

cheers,
        Oliver


Other related posts: