On Thu, Oct 09, 2003 at 12:32:53AM +0200, Slaven Rezic wrote: > Tatsuhiko Miyagawa <miyagawa@edge.co.jp> writes: > > Program received signal SIGSEGV, Segmentation fault. > > 0x281f1a95 in readdir_r () from /usr/lib/libc_r.so.4 > > (gdb) bt > > #0 0x281f1a95 in readdir_r () from /usr/lib/libc_r.so.4 > > #1 0x80e2139 in Perl_pp_readdir () > > #2 0x80ab1a1 in Perl_runops_standard () > > #3 0x8061d09 in S_run_body () > > #4 0x80619d8 in perl_run () > > #5 0x805e816 in main () > > #6 0x805e6f5 in _start () > > (gdb) > > > > > > should I rebuild perl to show full backtrace? I'm not sure if you need to. Given that the SEGV is in the libc_r code, I don't think that it's perl's fault, and I can't see how we can avoid tickling the bug. > FYI: no segfault with a threaded perl 5.8.1 on a slightly newer > FreeBSD (4.6). Maybe it's a race condition. How many CPUs does your box have. How many does Tatsuhiko Miyagawa's box have? Nicholas ClarkThread Previous | Thread Next