Custom Query (204 matches)
Results (184 - 186 of 204)
| Ticket | Owner | Reporter | Resolution | Summary |
|---|---|---|---|---|
| #197 | duplicate | man: LIBC panic if run from root dir | ||
| Description |
man 2.7.6.1-2 (i686) gets us: man.exe: fork failed: No such file or directory LIBC PANIC!! LIBC fork: Child aborting fork()! rc=0xfffffffe when run from \. Changing to any subdirectory one or more levels deep, whether in %PATH% or not, alleviates the symptom. I know we've seen this with other things (yum, for example, or python; see https://trac.netlabs.org/rpm/ticket/252). The more likely solution for this is in LIBC or perhaps LIBCX. Feel free to close this when an appropriate ticket is opened. Sorry to be a nuisance with this one. |
|||
| #199 | worksforme | heimdal-devel is missing various files critical for development | ||
| Description |
smbcln47.dll and smbnetap.dll are included in the heimdal-libs package. However, the heimdal-devel package, which includes the lib (.a) files for other libraries in heimdal-libs, does not include either smbcln47.a or smbnetap.a (although it does contain map files for both DLLs). Nor does any other extant rpm. Consequently there is no way to link programs to either DLL using the packages provided. Also, the package does not contain any header files either, even though the description states: "Header and other development files for Heimdal kerberos". This makes building programs using any Heimdal APIs difficult. |
|||
| #204 | fixed | pthread: wrlock() causes CPU load to 99.9% and tryrdlock()/trywrlock() falls into deadlock | ||
| Description |
Hi/2. Let's see the following case.
In 2., CPU load gets to 99.9% because of a tight loop in pthread_rwlock_wrlock(). And In 3., deadlock occurs in pthread_rwlock_tryrdlock() because lock->mutex is not released in pthread_rwlock_wrlock(). This occured in the test of pthread_rwlock_rdlock.m4. |
|||
