Re: problems with threads/destructors in -current with llvm/clang

2012-12-10 Thread Ryan Stone
On Mon, Dec 10, 2012 at 12:35 PM, Mark Atkinson wrote: > vex x86->IR: unhandled instruction bytes: 0xF 0xB 0x90 0x90 > ==33074== valgrind: Unrecognised instruction at address 0x380434e9. > ==33074==at 0x380434E9: ??? (in > /usr/local/lib/valgrind/memcheck-x86-freebsd) > ==33074==by 0x323C

Re: problems with threads/destructors in -current with llvm/clang

2012-12-10 Thread Konstantin Belousov
On Mon, Dec 10, 2012 at 01:13:23PM -0800, Mark Atkinson wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 12/10/2012 12:45, Mark Atkinson wrote: > > On 12/10/2012 12:33, Konstantin Belousov wrote: > > > >> Hmm. Since I took out -O2 and added -g in rebuilding > >> libthr/libc/rtld,

Re: problems with threads/destructors in -current with llvm/clang

2012-12-10 Thread Mark Atkinson
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/10/2012 12:45, Mark Atkinson wrote: > On 12/10/2012 12:33, Konstantin Belousov wrote: > >> Hmm. Since I took out -O2 and added -g in rebuilding >> libthr/libc/rtld, I figured I needed to reproduce a new >> segfault, but the rtld side of things

Re: problems with threads/destructors in -current with llvm/clang

2012-12-10 Thread Mark Atkinson
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/10/2012 12:33, Konstantin Belousov wrote: > Hmm. Since I took out -O2 and added -g in rebuilding > libthr/libc/rtld, I figured I needed to reproduce a new segfault, > but the rtld side of things seems broken: >> Use e.g. cd src/libexec/rtld-el

Re: problems with threads/destructors in -current with llvm/clang

2012-12-10 Thread Konstantin Belousov
On Mon, Dec 10, 2012 at 12:29:20PM -0800, Mark Atkinson wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 12/10/2012 10:25, Konstantin Belousov wrote: > > On Mon, Dec 10, 2012 at 09:35:29AM -0800, Mark Atkinson wrote: On > > 12/07/2012 09:29, Dimitry Andric wrote: > On 2012-12-0

Re: problems with threads/destructors in -current with llvm/clang

2012-12-10 Thread Mark Atkinson
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/10/2012 10:25, Konstantin Belousov wrote: > On Mon, Dec 10, 2012 at 09:35:29AM -0800, Mark Atkinson wrote: On > 12/07/2012 09:29, Dimitry Andric wrote: On 2012-12-07 17:43, Mark Atkinson wrote: > On 12/7/2012 6:08 AM, Dimitry Andric wrot

Re: problems with threads/destructors in -current with llvm/clang

2012-12-10 Thread Konstantin Belousov
On Mon, Dec 10, 2012 at 09:35:29AM -0800, Mark Atkinson wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 12/07/2012 09:29, Dimitry Andric wrote: > > On 2012-12-07 17:43, Mark Atkinson wrote: > >> On 12/7/2012 6:08 AM, Dimitry Andric wrote: > > ... > >>> With this patch (placed in /u

Re: problems with threads/destructors in -current with llvm/clang

2012-12-10 Thread Mark Atkinson
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/07/2012 09:29, Dimitry Andric wrote: > On 2012-12-07 17:43, Mark Atkinson wrote: >> On 12/7/2012 6:08 AM, Dimitry Andric wrote: > ... >>> With this patch (placed in /usr/ports/devel/dbus-qt4/files), >>> qdbus starts up and exits normally for me.

Re: problems with threads/destructors in -current with llvm/clang

2012-12-07 Thread Kevin Lo
Dimitry Andric wrote: > On 2012-12-07 13:59, Dimitry Andric wrote: > > On 2012-12-06 18:12, Mark Atkinson wrote: > >> Short backstory, I had recently upgraded my workstation to the latest > >> current which included clang as default cc now. > > ... > >> qdbus under kde segfaults in malloc with a hu

Re: problems with threads/destructors in -current with llvm/clang

2012-12-07 Thread Dimitry Andric
On 2012-12-07 17:43, Mark Atkinson wrote: On 12/7/2012 6:08 AM, Dimitry Andric wrote: ... With this patch (placed in /usr/ports/devel/dbus-qt4/files), qdbus starts up and exits normally for me. I did not do any other rigorous testing, though. :) Thanks for the awesome analysis. I will endea

Re: problems with threads/destructors in -current with llvm/clang

2012-12-07 Thread Mark Atkinson
On 12/7/2012 6:08 AM, Dimitry Andric wrote: > On 2012-12-07 13:59, Dimitry Andric wrote: >> On 2012-12-06 18:12, Mark Atkinson wrote: >>> Short backstory, I had recently upgraded my workstation to the latest >>> current which included clang as default cc now. >> ... >>> qdbus under kde segfaults

Re: problems with threads/destructors in -current with llvm/clang

2012-12-07 Thread Dimitry Andric
On 2012-12-07 13:59, Dimitry Andric wrote: On 2012-12-06 18:12, Mark Atkinson wrote: Short backstory, I had recently upgraded my workstation to the latest current which included clang as default cc now. ... qdbus under kde segfaults in malloc with a huge recursion stack: ... This is a bug in

Re: problems with threads/destructors in -current with llvm/clang

2012-12-07 Thread Dimitry Andric
On 2012-12-06 18:12, Mark Atkinson wrote: Short backstory, I had recently upgraded my workstation to the latest current which included clang as default cc now. ... qdbus under kde segfaults in malloc with a huge recursion stack: [...] #44740 0x282f7bd4 in QObject::QObject () from /usr/local/li

problems with threads/destructors in -current with llvm/clang

2012-12-06 Thread Mark Atkinson
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Short backstory, I had recently upgraded my workstation to the latest current which included clang as default cc now. Compiling chromium failed for want of SSE2, which led me to recompile world with CPUTYPE?=core2. The original flag for world/ports