Re: Many core dumps in pthread_getspecific.

Hi, On 27 July 2015 at 22:41, Adrian Chadd wrote: > What was that option actually doing? How'd it break things? old operating systems like Windows 98 can't handle a CPUID higher than 3. But Pentium 4 with HTT (Hyper-Threading Technologie) has a higher value. So the BIOS can limit it to 3. Th

Re: Many core dumps in pthread_getspecific.

Kudos to Konstantin Belousov! I'm not sure if this list was interested into all this error tracking. So we made the error tracking with private mails. Anyway, it was a BIOS setting named "limit CPUID maximum" and I had to disable it (BIOS help said "disabled for Windows XP"). Thank you Konsta

Re: Many core dumps in pthread_getspecific.

On Sun, Jul 19, 2015 at 22:57 +0200, Konstantin Belousov wrote: > It seems that besides sigreturn(), ucontext symbols must be pre-resolved > as well. Try this update (it includes the previous change). thanks for looking into this, but this patch wasn't funny at all. Did you tested your patch?

Re: Many core dumps in pthread_getspecific.

Hi, no crash from vim or Xorg but from xterm and again at getcontext(uc) after alloca: % readelf -d xterm | grep NEEDED 0x0001 (NEEDED) Shared library: [libXinerama.so.1] 0x0001 (NEEDED) Shared library: [libXft.so.2] 0x0001 (NEEDED)

Re: Many core dumps in pthread_getspecific.

On Fri, Jul 03, 2015 at 23:11:50PM +0200, Konstantin Belousov wrote: > You would be wrong. Wow, I should start learning how to dig into those core dumps... > Try the following patch, but I am unsure how easy is to > see whether the patch helps. I've patched my system. I can't reproduce the bug

Re: Many core dumps in pthread_getspecific.

Hi, back again. Sorry, I accidently deleted the core file and I'd to wait two weeks until vim crashed again. Xorg didn't crashed so far with the debug libs. On Tue, Jun 16, 2015 at 09:36 +0200, Konstantin Belousov wrote: > Ok, so the vim fault is reproducable, I suppose ? No, I tried, but no ch

Re: Many core dumps in pthread_getspecific.

On Sun, Jun 14, 2015 at 21:05 +0200, Konstantin Belousov wrote: > Show me the 'ldd vim' output and output from the > readelf -d vim | grep NEEDED. % ldd /usr/local/bin/vim /usr/local/bin/vim: libm.so.5 => /lib/libm.so.5 (0x800a55000) libncurses.so.8 => /lib/libncurses.so.8 (0x800c7

Aw: Re: Many core dumps in pthread_getspecific.

Hi, On Wed, Jun 03, 2015 at 16:58 +0200, Konstantin Belousov wrote: > You should recompile both libc and libthr with debugging symbols, like > cd /usr/src > (cd lib/libc && make all install DEBUG_FLAGS=-g) > (cd lib/libthr && make all install DEBUG_FLAGS=-g) > then obtain the core dump and post ba

Re: Many core dumps in pthread_getspecific.

On Wed, Jun 03, 2015 at 16:58 +0200, Konstantin Belousov wrote: > You should recompile both libc and libthr with debugging symbols, like > cd /usr/src > (cd lib/libc && make all install DEBUG_FLAGS=-g) > (cd lib/libthr && make all install DEBUG_FLAGS=-g) > then obtain the core dump and post backtra

Many core dumps in pthread_getspecific.

Hi, I'm new to FreeBSD and I'm running into a lot of core dumps (mainly from Xorg, but also from vim, firefox, ...). That's why I asked on freebsd-questions: https://lists.freebsd.org/pipermail/freebsd-questions/2015-June/266138.html https://lists.freebsd.org/pipermail/freebsd-questions/2015-Jun