At 04:25 PM 7/8/99 +0100, you wrote:
> -----Original Message-----
> From: Paul Kinnucan [SMTP:[EMAIL PROTECTED]]
>
>---------------------------------------------------------------------
> VM_ID CMD_ID get_threads
>
>
>It would be useful if monitor information could also be returned, either in
>this command or in another, ie list of monitor held and monitors being
>waited on.
>
>
Good suggestion. We'll provide support for this.
>
>----------------------------------------------------------------------
> VM_ID CMD_ID get_thread_groups
>
> Returns all the thread groups defined for VM_ID
>
>
>-----------------------------------------------------------------------
> VM_ID CMD_ID get_stack_on_thread THREAD_ID
>
> Returns the stack of the method in which the thread specified by
> THREAD_ID is currently located. Once the JDE has this stack, it
> should be able to use jdebug's stack navigation commands (up/down)
> to explore the call stack of the specified thread.
>
>
>
>-----------------------------------------------------------------------
> VM_ID CMD_ID set_breakpoint_on_thread CLASS LINE_NO THREAD_ID
>
>Is a break point on an exception possible? In particular if the thread
>throws an uncaught exception, eg null pointer exception, it's going to exit,
>unless it can be caught by the debugger at the point it is thrown.
>
>
Perhaps we should generalize the set_breakpoint command as follows:
VM_ID CMD_ID set_breakpoint [(in CLASS) ((at_line L) | (at_method M))]
[CONDITION)]*
where condition is any of the following expressions
on_exception CLASS
if_thread THREAD_ID
on_thread_dies THREAD_ID
if "boolean expression"
Examples:
1 1 set_breakpoint in FooBar at-line 100 if "firstName == \"Paul\""
if_thread 56
1 2 set_breakpoint on_exception java.io.FileNotFound if_thread 56
2 1 set_breakpoint on_thread_dies 56
>
>-----------------------------------------------------------------------
> VM_ID CMD_ID set_single_thread_mode [on | off]
>
>What happens to the other threads during this? Are they suspended or do they
They continue to run. If you do step in the current thread and the thread is
suspended as a result, the other threads run until the current thread regains
control.
>continue to run. It would, as ever, be useful to be able to choose what the
>other threads do.
>
Do you mean you want debugger commands that suspend or activate threads
independently of debuggee logic? If you do and that's possible, we should
provide the commands.
Amit, your thoughts?
>Also if the thread being debugged dies, it may be useful if the program can
>break, rather than just letting all the other threads run, because it
>probably wasn't meant to exit.
>
ok
>--
>Matt
>
>
>
>
>
>##########################################
>This email, its content and any files transmitted with it are intended
>solely for the addressee(s) and may be legally privileged and/or
>confidential. Access by any other party is unauthorised without the
>express written permission of the sender. If you have received this
>email in error you may not copy or use the contents, attachments or
>information in any way. Please destroy it and contact the sender on
>the number printed above, via the Dresdner Kleinwort Benson
>switchboard on +44 171 623 8000 or via e-mail return. Internet
>communications are not secure unless protected using strong
>cryptography. This email has been prepared using information believed
>by the author to be reliable and accurate, but Dresdner Kleinwort
>Benson makes no warranty as to accuracy or completeness. In particular
>Dresdner Kleinwort Benson does not accept responsibility for changes
>made to this email after it was sent. Any opinions expressed in this
>document are those of the author and do not necessarily reflect the
>opinions of the Bank or its affiliates. They may be subject to change
>without notice.
>##########################################
