debugging threads vs processes
Fri Jul 13 13:44:00 GMT 2001
The current lack of distinction between threads and processes on
is really annoying. For example when debugging a multi-threaded process
one must type `continue' for every thread to restart the application.
On a typical
Java or multithreaded application this requires maybe a dozen
you never know if you've actually hit another breakpoint or just
thread stopped by the first ^C or breakpoint.
Personally, I can't see much point in having a separate `ps' or `top'
each thread entry, since all entries show exactly the same information
for the process ID. And killing a process is a nightmare. If you're
to have only one process running the application, then `killall
However it gets really messy to figure out which of the hundreds of
threads in `ps' correspond to the process you really want to kill.
On Friday, July 13, 2001, at 01:16 PM, Cedric Berger wrote:
> 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
> between 10 to 30 thread. Do you think Linux "top" output is very useful
> my server? And I need to write a shell script just to kill one
> process :(
More information about the Java