Bug 59614 – top shouldn't display multithreaded apps once per thread

Bug 59614 - top shouldn't display multithreaded apps once per thread

Summary:	top shouldn't display multithreaded apps once per thread

Status:	CLOSED DEFERRED

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	procps (Show other bugs)
Sub Component:
Version:	7.2
Hardware:	i386 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Michael K. Johnson
QA Contact:	Aaron Brown
Docs Contact:

URL:
Whiteboard:
Keywords:	FutureFeature

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2002-02-11 04:40 EST by Havoc Pennington
Modified:	2007-04-18 12:40 EDT (History)
CC List:	1 user (show)

See Also:
Fixed In Version:
Doc Type:	Enhancement
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2002-02-11 04:40:06 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Havoc Pennington 2002-02-11 04:40:01 EST

If one more confused user mails the list and asks why they have 6 mozillas or 4
nautiluses, I think I'm going to go insane. ;-)

It should really display a multithreaded app only once. Or at least somehow 
indicate that the threads are only threads.

Comment 1 Arjan van de Ven 2002-02-11 04:56:34 EST

Until glibc's threading is changed to actually use the Thread GID's the kernel
provides there's no point in top also using them..... And there's no other way
to find out if 2 proccesses happen to be a thread.

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