Hello. > Hi Petr, ( I read debian-bsd, so no need to CC me explicitly,)
> Program received signal ?, Unknown signal. > 0x00000008019347d7 in __pthread_sigsuspend () from /lib/libpthread.so.0 ... > I posted this to upstream devel list[1] and they responded: > > At the first glance this looks like broken kFreebsd/amd64. Yes, the failure is in our side, we still have to teach gdb somehow, that thread handling is the same as in linuxthreads (pre-NPTL) implementation, see #550361. Unfortunately it requires deep knowledge of gdb, which no-one porter have :-( > How likely does it seem to you that the problem is in threading stuff > on kfreebsd/amd64? We have problem in threaded gdb support, but it does not seems we have general problem with threads. The implementation is the same on both kfreebsd-i386 and kfreebsd-amd64. Take a look on my ktrace: 45835 gbak_static CALL flock(0xa,LOCK_UN) 45835 gbak_static RET flock 0 45835 gbak_static CALL close(0xa) It seems normal - unlock file and close file 45835 gbak_static CALL close(0xa) 45835 gbak_static RET close -1 errno 9 Bad file descriptor And this is strange - close again the same file, which have been closed two syscalls above ? Do you have idea about differences between firebird2.1 (builds fine) and firebird2.5 (FTBFS) ? Petr -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
