Bug 54262 - Freeze with multithread app under kernel 2.4.10
Freeze with multithread app under kernel 2.4.10
Product: Red Hat Raw Hide
Classification: Retired
Component: gdb (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Trond Eivind Glomsrxd
Aaron Brown
Depends On:
  Show dependency treegraph
Reported: 2001-10-02 12:31 EDT by Miguel Freitas
Modified: 2007-04-18 12:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-10-02 12:31:41 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Miguel Freitas 2001-10-02 12:31:34 EDT
Description of Problem:

I used to debug Xine (a gpl video player, heavly multithreaded)
with gdb-5.0rh-16 without any problems. Upgrading to 2.4.10
makes xine freeze under gdb at a pthread_create function.
Turning back to 2.4.9 fixes the problem (however i like 2.4.10
performance! :)

(I know this issue must be evaluated with care given the
"experimental" VM just integrated into kernel. However i 
think this kind of change must not have influence over
user space apps).

Version-Release number of selected component (if applicable):

How Reproducible:

Steps to Reproduce:
1.install kernel 2.4.10
2.get xine sources (http://xine.sf.net)
3.make debug; sudo make install-debug
4.run xine under gdb
Actual Results:
During initialization Xine creates several threads. It seems
to freeze at the very first of them.

Expected Results:
It would just finish initializing and work!

Additional Information:
Program compiled with gcc-2.96rh-97, using glibc-2.2.4-8.
Comment 1 Trond Eivind Glomsrxd 2001-10-04 15:21:40 EDT
Reopen if it happens with a kernel we support. 2.4.10 is known to be broken in
many areas.
Comment 2 Miguel Freitas 2001-10-07 18:13:38 EDT
Just a quick note: the problem is gone with kernel 2.4.11-pre4

Note You need to log in before you can comment on or make changes to this bug.