On Wed, Nov 01, 2000 at 19:17:26 +0200, Maxim Sobolev wrote:
> 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.
> #0 0x287de417 in pthread_mutex_lock () from /usr/lib/libc_r.so.4
Same for me in -stable (4.2-BETA) and python-1.6. After rebuilding the port
this disappeared. My gdb showed the same error message as the quoted above.
Udo Schweigert, Siemens AG | Voice : +49 89 636 42170
ZT IK 3, Siemens CERT | Fax : +49 89 636 41166
D-81730 Muenchen / Germany | email : [EMAIL PROTECTED]
PGP-2/5 fingerprint | D8 A5 DF 34 EC 87 E8 C6 E2 26 C4 D0 EE 80 36 B2
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message