× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Hi,

Has anyone encountered an issue with RDP 8.5 LOCKING UP for no reason when ending debug?

I happen to be debugging a file. And I then ended debug. But my green screen session is locked up on a VERY SIMPLE test program. Send a message to a file. Program has About 10 lines of code.

I had to manually kill JAVA.EXE & Eclipse.EXE...
<Frown> apparently, my guess, is that "SOMEHOW" that RDP LOCKED my Green Screen Session. How, I do NOT KNOW HOW...

Anyway, after KILLING RDP 8.5, which did NOT lock up. My lock problem on the Green Screen "LOCK" goes away....
<Perplexed look>

Strange, I now remember the other reason I downgraded to RDP 8.0.3. It was also because of this "LOCK-UP" problem.
Hard to re-create, because I do NOT know exactly what creates/causes this...

This is on a newly formatted PC with Window 7 with a clean install for RDP 8.5.

Has anyone else experienced "LOCK-UP" problems with RDP 8.5? Anyone found any resolutions for this issue?

Restarting RDP 8.5, I notice this error log:
An exception occurred during breakpoint change notification.

eclipse.buildId=unknown
java.fullversion=JRE 1.7.0 IBM J9 2.6 Windows 7 amd64-64 20110810_88604 (JIT enabled, AOT enabled)
J9VM - R26_Java726_GA_20110810_1208_B88592
JIT - r11_20110810_20466
GC - R26_Java726_GA_20110810_1208_B88592
J9CL - 20110810_88604
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US
Framework arguments: -product com.ibm.rational.rdpower.product.ide
Command-line arguments: -os win32 -ws win32 -arch x86_64 -product com.ibm.rational.rdpower.product.ide

This is a continuation of log file C:\Users\kkillian\IBM\rationalsdp\workspace_8_5\.metadata\.bak_6.log
Created Time: 2012-10-23 06:36:54.677


Error
Tue Oct 23 13:48:57 EDT 2012
An exception occurred during breakpoint change notification.

java.util.ConcurrentModificationException
at java.util.HashMap$AbstractMapIterator.checkConcurrentMod(Unknown Source)
at java.util.HashMap$AbstractMapIterator.makeNext(Unknown Source)
at java.util.HashMap$KeyIterator.next(Unknown Source)
at java.util.AbstractCollection.toArray(Unknown Source)
at com.ibm.debug.pdt.ui.DebuggerMarkerAnnotationModel.resetMarkers(Unknown Source)
at com.ibm.debug.pdt.ui.DebuggerMarkerAnnotationModel.breakpointAdded(Unknown Source)
at org.eclipse.debug.internal.core.BreakpointManager$BreakpointNotifier.run(Unknown Source)
at org.eclipse.core.runtime.SafeRunner.run(Unknown Source)
at org.eclipse.debug.internal.core.BreakpointManager$BreakpointNotifier.notify(Unknown Source)
at org.eclipse.debug.internal.core.BreakpointManager.fireUpdate(Unknown Source)
at org.eclipse.debug.internal.core.BreakpointManager.addBreakpoints(Unknown Source)
at org.eclipse.debug.internal.core.BreakpointManager.addBreakpoints(Unknown Source)
at org.eclipse.debug.internal.core.BreakpointManager.addBreakpoint(Unknown Source)
at com.ibm.debug.pdt.core.breakpoints.PICLBreakpoint.registerBreakpoint(Unknown Source)
at com.ibm.debug.pdt.core.breakpoints.PICLBreakpoint.<init>(Unknown Source)
at com.ibm.debug.pdt.core.breakpoints.PICLEventBreakpoint.<init>(Unknown Source)
at com.ibm.debug.pdt.core.breakpoints.PICLWatchBreakpoint.<init>(Unknown Source)
at com.ibm.debug.pdt.core.breakpoints.PICLBreakpoint.createPICLBreakpoint(Unknown Source)
at com.ibm.debug.pdt.internal.core.PDTDebugTarget$1.run(Unknown Source)
at org.eclipse.core.internal.jobs.Worker.run(Unknown Source)



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.