Bug 104762 - multi threaded core dump missing thread information
multi threaded core dump missing thread information
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Arjan van de Ven
Brian Brock
Depends On:
  Show dependency treegraph
Reported: 2003-09-20 13:52 EDT by Sergey Kosenko
Modified: 2007-04-18 12:57 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-09-30 11:41:32 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 Sergey Kosenko 2003-09-20 13:52:02 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; T312461; 
Q312461; .NET CLR 1.0.3705; .NET CLR 1.1.4322)

Description of problem:
Core dump of application compiled with pthread and intensionally crushed is 
missing all but one thread information.

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

How reproducible:

Steps to Reproduce:
1.ulimit -c unlimited
2.compile with gcc 3.2.3
4.open dumped core in gdb 5.3
5.enter "info thread" in gdb

Actual Results:  gdb shows one thread

Expected Results:  there should be at least two thread if it crashes in the 
thread code.


#include <pthread.h>

#define NUM_THREADS 2
#define SLEEP_TIME 1 

void *sleeping(void *); 

main(int argc, char *argv[])
   int i; 
   thread_t tid[NUM_THREADS]; 

   for ( i = 0; i < NUM_THREADS; i++ )
      pthread_create(&tid[i], NULL, sleeping, (void *)0);


   for ( i = 0; i < NUM_THREADS; i++ )
      pthread_join(tid[i], NULL);

void *
sleeping(void *arg)
   int a, *b = 0;
   a = *b; // <<----- crash
Comment 1 Bugzilla owner 2004-09-30 11:41:32 EDT
Thanks for the bug report. However, Red Hat no longer maintains this version of
the product. Please upgrade to the latest version and open a new bug if the problem

The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases, 
and if you believe this bug is interesting to them, please report the problem in
the bug tracker at: http://bugzilla.fedora.us/

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