Bug 816
Summary: | egcs pthread bug | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | m_vogt |
Component: | egcs | Assignee: | Nalin Dahyabhai <nalin> |
Status: | CLOSED WORKSFORME | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 5.2 | CC: | gafton |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | alpha | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 1999-08-30 01:21:35 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
m_vogt
1999-01-13 10:36:17 UTC
Are the other kde libraries linked in the example thread safe? Is this still valid on the RH 6.0? assigned to pbrown for follow ups. This still happens under RHL 6.0 on alpha. Cristian, even if the kde libraries aren't thread safe, all the KDE/X stuff is being done in one thread, so it shouldn't segfault, right? I am no linking expert, but this behaviour does seem strange to me too. Jim, can you please take a look into this? What libraries do I need to use to reproduce this bug? I tried it on a few systems here and I just got things like: /usr/include/kconfigbase.h:80: qcolor.h: No such file or directory It looks like it may be a real bug (link order does matter, but getting it wrong should not - usually - cause core dumps). Preston, is there a machine at redhat (say a chroot jails on porky/jetson?) which can reproduce this? |