Killing the process can cause breakpoints to have a stale jdwp

[GoogleCodeExporter]

What steps will reproduce the problem?
1.  Connect the debugger to a running process
2.  Set breakpoints that are resolved.
3.  Kill the process without using jdibug-disconnect
4.  Start another process and connect to the debugger.
5.  Go to one of the break points, type C-c C-c C-b (jdibug-toggle-breakpoint)

What is the expected output? What do you see instead?
The breakpoint should cycle through enabled, disabled and deleted.

Instead, there is a message that <#process jdwp> is not active.

Please use labels and text to provide additional information.

Original issue reported on code.google.com by udalrich.schermer on 14 Apr 2010 at 5:35