Mike Hall wrote:
| Launching command line from terminal is whats supposed to allow the ctrl+\ stack crawls I think.
Ctrl-\ merely sends the QUIT signal to the current process (the one controlling the Terminal window at the moment). The "kill" command sends it to another process. The JVM does the same thing regardless of where the QUIT comes from. What's likely to differ is what the "standard output" is at the time the signal is sent. For ctrl-\, it'll be the Terminal window, unless it's been redirected. For some other process, it's most likely the console log, unless the other process was also started from Terminal.
| Launching the application this way might make it more responsive to the kill signal.
Nope. Whether an application responds (or not) to a signal is entirely up to the application.
| Isn't kill -QUIT whats supposed to actually get you a current stack
| crawl? Unless thats same as -6 I'm not sure on that either.
Look in "/usr/include/sys/signal.h" for a complete number-to-name mapping.
| There were some odds and ends in the developer tools install. This
| included some process watcher and I think killer that might work.
I suspect you're thinking of "Process Viewer" (Jaguar) or "Activity Monitor" (Panther), which aren't developer tools, but utilities (in /Applications/Utilities). They can kill the process (using, I believe, the TERM signal), but can't send any other signals.
Glen Fisher
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Java-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/java-dev/email@hidden
This email sent to email@hidden
