debugging threads vs processes

Fri Jul 13 13:16:00 GMT 2001

"Boehm, Hans" wrote:
> > -----Original Message-----
> > From: Cedric Berger [ mailto:cedric@wireless-networks.com ]
> > There is clearly good things with LinuxThreads (i.e. simplicity, ...)
> > But as long as, at least...
> > - top
> > - ps
> > - kill
> > - gdb
> >
> > ... are not fixed, and to not really understand the
> > difference between a thread
> > and a process, using multithreaded application in Linux will
> > remain a huge pain.
> >
> I think some of this depends on what you're used to. I've adapted to the
> top and ps behavior, and I often find it useful that I can see the threads
> separately. If it automagically told me whether something was the main
> thread, the manager, or another thread, that would be better still. If it
> showed me only processes, I'd be less happy.

I agree there is certainly some situations where the current behavior is
useful. *BUT* there *MUST* be a switch on theses command which
only show/use *PROCESSES*.
I've currently 8 Java server application running on my server, each creating
between 10 to 30 thread. Do you think Linux "top" output is very useful on
my server? And I need to write a shell script just to kill one process :(
Cedric