Return Styles: Pseud0ch, Terminal, Valhalla, NES, Geocities, Blue Moon.

Pages: 1-

threads & tools

Name: Anonymous 2010-11-24 14:15

Hi,

Let's say I have a process with multiple threads inside, is there a tool, that will tell which threads eats the biggest amount of memory and CPU, which are most of the time idle, what is current state of all of threads, in which threads segmentation fault (or other bug) bug appears? It would be also nice if it could say witch one didn't deallocate memory (new, malloc, etc) when process is terminating.

This must work on Linux, but it would be nice if I could run it on Windows and Mac too. Also CLI is "must have".

AFAIK valgrind with its extension could be used for this, but I didn't try it yet, have you got better tools?

Name: Anonymous 2010-11-24 15:50

top(1)

Name: Anonymous 2010-11-24 16:18

Yes, but top (we talk about Linux top, right?) show info only about processes, not about their threads? If not, could you provide sample usage of top in this case?

Name: Anonymous 2010-11-24 17:35

which threads eats the biggest amount of memory
I have bitch tits.

Name: Anonymous 2010-11-24 17:48

I find this thread subtly amusing

Name: Anonymous 2010-11-24 18:15

AFAIK valgrind with its extension could be used for this, but I didn't try it yet, have you got better tools?
Why don't you tr-- Never mind. My bitch tits are in the way.

Name: Anonymous 2010-11-24 19:17

htop

Name: Anonymous 2010-11-25 16:21

Yeah, htop will be useful, thanks dude!
Any other (non retarded) ideas/comments?

Name: Anonymous 2010-11-25 16:25

>>8
Okay, now read the rest of the thread, and from htop, make a note on how much memory each thread consumes in relation to its parent process. Then read up on how threads work. Then become enlightened.

Name: Anonymous 2010-11-25 16:41

Anyway I think I will download sources and check how this tool was made.

Name: Anonymous 2010-11-25 17:38

>>10
Anyway I think you you sage when you don't have anything meaningful to contribute.

Name: Anonymous 2010-11-25 17:51

You're right, I should use sage this time.

Name: Anonymous 2010-11-25 19:40

Anyway I think I'm going to bump this because >>11 is a faggot.

Name: Anonymous 2010-11-25 23:58

>>1
replace your threads with multiple processes.

Don't change these.
Name: Email:
Entire Thread Thread List