tags 236816 + unreproducible quit Hi Vincent,
Vincent Lefevre wrote: > Program terminated with signal 11, Segmentation fault. [...] > #0 0x400f4b7a in fseek () from /lib/libc.so.6 > #1 0x40039e0c in bfd_seek () from /usr/lib/libbfd-2.13.90.0.10.so > #2 0x4005a5ba in bfd_elf_get_elf_syms () from /usr/lib/libbfd-2.13.90.0.10.so > #3 0x400576f1 in bfd_elf32_bfd_final_link () > from /usr/lib/libbfd-2.13.90.0.10.so > #4 0x40055800 in bfd_elf32_bfd_final_link () > from /usr/lib/libbfd-2.13.90.0.10.so > #5 0x08058acd in bfd_link_hash_lookup () > #6 0x08056bd6 in bfd_link_hash_lookup () > #7 0x400a70bf in __libc_start_main () from /lib/libc.so.6 > > This is not reproducible, but I had similar problems on a different > machine (as and ld segfault). Both are multiprocessor machines and > this may be the problem. AFAIK, I've never had a crash on a single- > processor machine. > > Also, note that the C source was under NFS in both cases and was > generated by a script just before the compilation. Thanks for a clear report. I suppose a diligent person should check under what conditions fseek might have segfaulted so this seems useful even without being reproducible. Still, it can't hurt to ask: have you ever experienced something like this sense then? Maybe there should be a binutils-dbg package to make a full backtrace easier to acquire in cases like this one. Sorry for the long silence, Jonathan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
