Hi,
I'm not sure what exactly caused this behaviour (I can guess two potential
victims: O'Brien's changes in crt stuff and recent Polstra's changes in
libgcc_r), but it seems that some programs built on the previous -current from
27 October immediately segfault when I'm trying to run then on system installed
from today's sources. The segfault disappeared when I recompiled affected
program. With this message I'm attaching short backtrace.
-Maxim
root@notebook# galeon
GNU gdb 4.18
This GDB was configured as "i386-unknown-freebsd"...
(no debugging symbols found)...
(gdb) r
Starting program: /usr/X11R6/bin/galeon-bin
(no debugging symbols found)...
[...]
(no debugging symbols found)...
Program received signal SIGSEGV, Segmentation fault.
0x287de417 in pthread_mutex_lock () from /usr/lib/libc_r.so.4
(gdb) bt
#0 0x287de417 in pthread_mutex_lock () from /usr/lib/libc_r.so.4
#1 0x806e782 in __register_frame_info ()
#2 0x287a3137 in _init () from /usr/lib/libc_r.so.4
#3 0x2879ffe5 in _init () from /usr/lib/libc_r.so.4
#4 0x280797fd in _rtld () from /usr/libexec/ld-elf.so.1
(gdb) q
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
