Debugger hangs

Hi,
Whenever I run the debugger, the IDE hangs. I can see debugger messages printed on the output window. The Windows window is OK - I can resize, minimize, etc., and Task Manager shows CPU usage etc. to be normal. But within the IDE all is dead - menus, buttons etc. don't respond to the mouse or the keyboard, and the windows don't redraw.
Has anybody seen this before? Any ideas about how to fix it?
I found some questions in the knowledge base on this site that mentioned setting the "classic debugger" property to false, which I've done.
Cheers,
Ciaran

No problem. But in any case, FYI: there is a well-known bug in JDK 1.4.1 and the debugger of Sun ONE Studio/NetBeans. The IDE hangs as a result of this bug. This affects all kinds of debugging, J2EE, J2SE and J2ME. This is currently being resolved. In the meantime, you can use the following workaround:
Install the previous version of the JDK, 1.4.0 and modify the ide.cfg in the <forte root>/bin directory to point to the older JDK.
Note: I've heard that people who have downgraded to JDK 1.3.1.xx find it easier to get the workaround to work.
You can also check out the Knowledge Base entry where this issue is addressed at http://forte.sun.com/cgi-bin/WebX?14@@.ee825d6.

Similar Messages

Debugger hanging !!!

Hi all,
unfortunately, I am the chosen for developing under Solaris, using Forte Develop 6.0.
When debugging my application, workshop becomes instable regularly; especially when using the 'Step Over (F7)' command. Workshop is hanging and will never return, so the only solution left is to exit workshop and start all over. I tried updating to 6.0 update 1, but then my class constructors are not handled correctly !!
And something else: the debugger always launches my 'main.cc' source file when started; what the fuck is that good for ???
I am really wondering whether this software is tested before it is released...
By the way: does anyone know how to switch off the fucking 'Re-usable' option in NEdit for ever ?
Yes, as you already may have concluded, I am NOT pleased with working under Forte Develop (and even the entire Solaris environment)...

Nope. I developed the whole core in debug mode of Flex Builder 3, so I know it works there.
Mike

Flex Builder 3 Debugger hanging unit tests

If I try to run my Unit Tests in debug mode from Flex Builder 3, FF and IE just hang until I cancel the debugger. Is this expected?

Nope. I developed the whole core in debug mode of Flex Builder 3, so I know it works there.
Mike

Flash Builder 4.5, debugger hanging at 57% need a solutions

I have been reviewing "All" the web solutions to my problem and have not found a solution. I have rebuild my work space so many times I can do it in my sleep. I have installed/uninstalled the flash player (debug version) again so many time I can do it in my sleep. I have rebooted and rebooted so many times I can tell how long it takes down to the second when my system will be available.
I am not an ID10T, yet I am starting to feel like one.
Here is my environment:
Windows (wishing it was an apple)
Browser(s): FireFox version 6
Flash Builder version 4.5
Flash player (latest debug version)
Attached snapshot from FlashPlayerVersion.com
As you can see from the image I have a debug version installed and the debugger options is disabled, this makes no sense to me and real assistance is appreciated.
Thank you
Harold
Just because one guy can make a baby in 9 months, doesn't mean 9 guys can do it in 1 --> Debug takes time not just bodies.

This is what I did and it worked fine, now I am really confused. Your
continued assistance is appreciated.
<?xml version="1.0" encoding="utf-8"?>
<s:Application xmlns:fx="http://ns.adobe.com/mxml/2009"
xmlns:s="library://ns.adobe.com/flex/spark"
xmlns:mx="library://ns.adobe.com/flex/mx" minWidth="955" minHeight="600">
<fx:Script>
<![CDATA[
import mx.controls.Alert;
protected function button1_clickHandler(event:MouseEvent):void
// TODO Auto-generated method stub
Alert.show("in...")
]]>
</fx:Script>
<fx:Declarations>

</fx:Declarations>
<s:Button x="52" y="110" label="Button"
click="button1_clickHandler(event)"/>
</s:Application

Informative: Debugger hangs, breaks server (XDebug, PDT 3.5?)

THIS TOPIC IS SUPERCEDED BY https://www.eclipse.org/forums/index.php/m/1700736
I had [in retrospect, small] debugging issues with Luna and decided to upgrade to Mars. I upgraded both Eclipse from 3.4 and PDT to 3.5. Just after, the debugger had severe breakage. It would go away, and apparently only come back after restarting Windows.
I then tried upgrading the WAMP stack (Apache 2.4.4 to 2.4.9, PHP 5.4.12 to 5.5.12, XDebug 2.2.3 to 2.2.5), and this seemed to solve the problem. But after a few days, it seems it just came back.
This was very frustrating, since online searches are difficult, but at least, after letting enough time, the affected project is again usable, and I got an error message when trying to debug again. It is surely not specific, but here it is:
Quote:The debug port 9000 is in use. Please select a different port for the debugger.
The UI's message is a bit different, this is actually from an exception which is generated when that error shows.
Since I have never seen that behavior with 3.4, a PDT 3.5 bug seems likely, but since it seems this doesn't affect that many people, I am just posting for information and will attempt to caracterize the issue better before going further.
STATUS
pluginId org.eclipse.php.debug.core
pluginVersion 3.5.0.201506101710
code 4
severity 4
message The debug port 9000 is in use. Please select a different port for the debugger.
fingerprint f5dbb25f
Exception:org.eclipse.epp.internal.logging.aeri.ui.log.StandInStacktraceProvider$StandInException: Stand-In Stacktrace supplied by the Eclipse Error Reporting
at org.eclipse.php.internal.debug.core.Logger._log(Logger.java:78)
at org.eclipse.php.internal.debug.core.Logger.log(Logger.java:136)
at org.eclipse.php.internal.debug.core.daemon.AbstractDebuggerCommunicationDaemon.handleMultipleBindingError(AbstractDebuggerCommunicationDaemon.java:143)
at org.eclipse.php.internal.debug.core.daemon.AbstractDebuggerCommunicationDaemon.resetSocket(AbstractDebuggerCommunicationDaemon.java:126)
at org.eclipse.php.internal.debug.core.xdebug.communication.XDebugCommunicationDaemon.resetSocket(XDebugCommunicationDaemon.java:398)
at org.eclipse.php.internal.debug.daemon.DaemonPlugin.validateCommunicationDaemons(DaemonPlugin.java:186)
at org.eclipse.php.internal.debug.core.launching.PHPLaunchUtilities.isDebugDaemonActive(PHPLaunchUtilities.java:1344)
at org.eclipse.php.internal.debug.core.launching.XDebugWebLaunchConfigurationDelegate.launch(XDebugWebLaunchConfigurationDelegate.java:154)
at org.eclipse.php.internal.debug.core.launching.PHPLaunchDelegateProxy.launch(PHPLaunchDelegateProxy.java:126)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039)
at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
REPORT
anonymousId a2e86edb-99b2-4ce2-87b9-8b1ac00206b6
name Filipus Klutiero
email [email protected]
comment
eclipseBuildId 4.5.0.I20150603-2000
eclipseProduct org.eclipse.epp.package.php.product
javaRuntimeVersion 1.8.0_31-b13
osgiWs win32
osgiOs Windows8
osgiOsVersion 6.2.0
osgiArch x86
logMessage false
ignoreSimilar false
BUNDLES
name org.eclipse.core.jobs
version 3.7.0.v20150330-2103
name org.eclipse.debug.core
version 3.10.0.v20150303-1130
name org.eclipse.debug.ui
version 3.11.0.v20150514-0917
name org.eclipse.php.debug.core
version 3.5.0.201506101710
name org.eclipse.php.debug.daemon
version 3.5.0.201506101710

This might be a conflict with one of your windows application (for example windows server sometime take it). Can you change debugger port?
This has to be done on both xdebug and eclipse, for example use port 1009:
1. Add xdebug.remote_port=1009 to php.ini and restart wamp
2. Set this port under Eclipse -> Preferences -> PHP -> Debug -> Debuggers -> XDebug
You might be also blocked by windows firewall.

Oracle 11GR2 Mapping Debugger Hangs

Hello All,
I am seeing an issue when trying to debug a mapping. This mapping is a simple mapping of three source tables, a joiner and a destination table. Every time i try to execute the full package not in debug i get no rows selected. Determined to figure out what the issue was i turned to the debugger which starts out just fine until it reaches generating debug package... step where it sits there anywhere from 5-30 mins before finally completing. Has anyone else seen this issue or have any suggestions on what it could be?
Thanks in advanced for any and all responses.
Note: It did not have this behavior in 11gR1 when I had a similar mapping.

Have you ever found an answer to this issue? We are seeing something very similar. A mapping in R1 took 30 seconds to begin debugging. The same mapping created in R2 takes 5 minutes to begin debugging.
We have had a support request open for 3 months on this with no resolution. We're using an XP client. They've had us increase the amount of memory allocated to the client using several flags, but the client never comes close to using that much. We don't know what the solution is, other than to not use debugging.
Any help anyone could provide would be appreciated.
Thanks,
Jayce

JDeveloper Debugger Hangs

Hi,
I have a solution with 2 web projects and a webcenter project. When i try to run de webcenter project, everything gets deployed and executed as expected. However, when i try to debug the same project, i get the following error in jdeveloper:
**oracle.webcenter.dt:Jul 13, 2011 2:24:29 PM oracle.webcenter.dt.utils.MDSUtil getMarEntry**
**WARNING: Could not create MAR entry for file [D:\...\.svn\text-base\pageTemplate_swooshyPageDef.xml.svn-base], due to: MDS-01161: Reference "/oracle/webcenter/portalapp/pagetemplates/.svn/text-base/pageTemplate_swooshyPageDef.xml.svn-base" has an invalid character ".".**
**Uncaught exception**
**java.lang.IllegalArgumentException: Invalid JNI signature character ';'**
**com.sun.tools.jdi.JNITypeParser.nextTypeName(JNITypeParser.java:218)**
**com.sun.tools.jdi.JNITypeParser.typeNameList(JNITypeParser.java:122)**
**com.sun.tools.jdi.JNITypeParser.typeName(JNITypeParser.java:67)**
**com.sun.tools.jdi.TypeImpl.name(TypeImpl.java:26)**
**com.sun.tools.jdi.ReferenceTypeImpl.compareTo(ReferenceTypeImpl.java:132)**
**com.sun.tools.jdi.ReferenceTypeImpl.compareTo(ReferenceTypeImpl.java:15)**
**j.util.TreeMap.put(TreeMap.java:545)**
**j.util.TreeSet.add(TreeSet.java:238)**
**com.sun.tools.jdi.VirtualMachineImpl.addReferenceType(VirtualMachineImpl.java:764)**
**com.sun.tools.jdi.VirtualMachineImpl.referenceType(VirtualMachineImpl.java:880)**
**com.sun.tools.jdi.EventSetImpl$ClassPrepareEventImpl.<init>(EventSetImpl.java:351)**
**com.sun.tools.jdi.EventSetImpl.createEvent(EventSetImpl.java:720)**
**com.sun.tools.jdi.EventSetImpl.build(EventSetImpl.java:611)**
**com.sun.tools.jdi.EventQueueImpl.removeUnfiltered(EventQueueImpl.java:193)**
**com.sun.tools.jdi.EventQueueImpl.removeInternal(EventQueueImpl.java:106)**
**com.sun.tools.jdi.InternalEventHandler.run(InternalEventHandler.java:36)**
**j.lang.Thread.run(Thread.java:662)**
Although the weblogic server seems to proceed with the startup, it just hangs indefinitely starting up one of the web projects.
How can i solve this issue?
Regards.

Hi
i have same issue
does any one has solution for this?
ct 11, 2011 9:34:26 PM oracle.webcenter.dt.utils.MDSUtil getMarEntry
WARNING: Could not create MAR entry for file [D:\JDeveloper\mywork\myportaapp\Portal\adfmsrc\oracle\webcenter\portalapp\pagetemplates\.svn\text-base\pageTemplate_swooshyPageDef.xml.svn-base], due to: MDS-01161: Reference "/oracle/webcenter/portalapp/pagetemplates/.svn/text-base/pageTemplate_swooshyPageDef.xml.svn-base" has an invalid character ".".
appreciate your help
thanks

Workshop 5.0 debugger hanging XSun setting breakpoints

I am running Solaris 2.6 and Workshop 5.0.
When I load a program and set a break-point, XSun goes loopie! It's process consumes > 98% CPU time. I have to kill it in order to get my system back.
I have installed the Solaris 2.6 recommended patch cluster, to no avail.
Any ideas?
-- jrj

I am running Solaris 2.6 and Workshop 5.0.
When I load a program and set a break-point, XSun goes loopie! It's process consumes > 98% CPU time. I have to kill it in order to get my system back.
I have installed the Solaris 2.6 recommended patch cluster, to no avail.
Any ideas?
-- jrj

WLS6.1 hanging on Solaris- and SIGQUIT doesn't work

Hi,
We are experiencing a problem that looks like a deadlock when our server is under load (using WLS6.1SP2, Solaris 8 and the 1.3.1 JVM supplied with WLS). After processing many requests, the server hangs and CPU usage drops to 0%. Unfortunately the standard means of getting a thread dump (sending a SIGQUIT with kill -3 or Ctrl-\) does nothing. The problem also occurs if WebLogic is running under debug (using
-Xdebug -Xnoagent -Djava.compiler=none -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=5555) but alas the debugger hangs when trying to pause the server after this deadlock). It appears as though the server is not accepting any requests (including administrative requests from the console) but this doesn't seem to be due to thread starvation as CPU usage is 0%.
The only output we can get is from truss, which seems to indicate no activity at all until the SIGQUIT is received. It seems to register the SIGQUIT but it looks as though it is not being processed.
Does anyone have any ideas?
Kevin.

We found a solution to this problem, relating to the threading model that the JVM
uses.
Have a look at http://java.sun.com/docs/hotspot/threads/threads.html for more
details.
The default threading model on Solaris 8 is many-to-many (threads to LWPs) with
thread-based synchronisation. After playing with various threading models, we
found that the best was one-to-one with the alternate thread library. This is
the default provided by Solaris 9, but you can also tell Java to use this with
older versions of Solaris by putting the following line in your start command
prior to executing WebLogic:
export LD_LIBRARY_PATH=/usr/lib/lwp:$LD_LIBRARY_PATH
Apologies to anyone who was looking for an answer to this beforehand: I should
have replied to this newsgroup back in September!
Kevin Thomas
J2EE Consultant
LogicaCMG
Charlie Therit <[email protected]> wrote:
Kevin,
If you are not able to capture a JVM thread dump, then the next best
thing would be to capture several "/usr/proc/bin/pstack pid" C-level
thread dumps. This information may enable BEA Support to help suggest
potential work arounds. Depending upon the data in the pstack output,
you may also wish to open a support case with Sun.
Sincerely,
Charlie Therit
Developer Relations Engineer
BEA Support
Kevin Thomas wrote:
Hi,
We are experiencing a problem that looks like a deadlock when our serveris under load (using WLS6.1SP2, Solaris 8 and the 1.3.1 JVM supplied
with WLS). After processing many requests, the server hangs and CPU
usage drops to 0%. Unfortunately the standard means of getting a thread
dump (sending a SIGQUIT with kill -3 or Ctrl-\) does nothing. The problem
also occurs if WebLogic is running under debug (using
-Xdebug -Xnoagent -Djava.compiler=none -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=5555)but alas the debugger hangs when trying to pause the server after this
deadlock). It appears as though the server is not accepting any requests
(including administrative requests from the console) but this doesn't
seem to be due to thread starvation as CPU usage is 0%.
The only output we can get is from truss, which seems to indicate noactivity at all until the SIGQUIT is received. It seems to register
the SIGQUIT but it looks as though it is not being processed.
Does anyone have any ideas?
Kevin.

Bug or change in CS5 Extendscript Toolkit debugger or parser

I got a strange error beginning to work with a script in CS5 (that is working in CS4, and has a script version setting making it run as CS4).
This is what happened: Pressing Step into code in ExtendScript Toolkit. The window switches to InDesign CS5. Nothing happens. I switch back to the toolkit environment, and there is the blue circle spinning at the bottom right, but nothing else happens.
The status row reads: No Errors
So I press stop, and then the following is written out in the status row (Bottom left of the Extendscript Toolkit CS5):
Cannot execute
Execution halted : Adobe InDesign CS5 did not respond
Trying to debug this error was not easy, since the debugger never entered the code. But at last I found a row containing a comment like this one:
//var sResult = '<![CDATA[' + a + ']]>';
Please will someone else put this code in a new script and see if you get the same effect:
//var sResult = '<![CDATA[' + a + ']]>';
var sResult = 'test';
alert(sResult);
The alert box is not showing up.
You can even minimize the code to this row in a script:
// ']]>';
That single comment in a script makes my debugger hang.
I hope there are no other secret character combinations that need to be removed for my script to run in CS5... Continuing my tests now.

@Andreas – I also ran into this bug a couple of months ago. However, I do not see this bug in the latest ESTK for InDesign CS6. Also, if I use the latest ESTK in conjunction with CS5.5 or CS5 I cannot provoke this error.
Seems this bug is fixed…
Here is some code to provoke this bug with ESTK 3.5.1.59 and InDesign CS5.5 v7.5.3:
//A text frame with a table is selected:
_Provoke_C_DATA_Error();
function _Provoke_C_DATA_Error(){
    var _d = app.activeDocument;
    var _table = app.selection[0].parentStory.tables[0];
    var _columns = _table.columns.everyItem().getElements();
    for(var c = 0;c<1;c++){
        var _cells = _columns[0].cells.everyItem().getElements();
        for(var n=_cells.length-1;n>0;n--){
            //Provokes C-DATA-Error with InDesign CS5 ESTK or InDesign CS5.5 ESTK
            //together with InDesign CS5.5 and InDesign CS6:
            $.writeln(_cells[n].contents);
}; //Function _Provoke_C_DATA_Error END
Uwe

[4.0 EA2] Debugger not stopping at breakpoints/not working at all

When running the debugger in SQL Developer either the debugger immediately connects then disconnects after executing the code WITHOUT stopping at breakpoints or the debugger hangs and the only actions I can choose is to terminate or to pause.
The first issue happens a lot more frequently. I am attempting to debug a procedure in a package where the there are several breakpoints throughout the code including at the very start. After checking my tables in which the procedure acts upon before and after running the debugger I can see that the data has been altered so the debugger has ran through the procedure and executed the code without stopping. I have checked this on very simple code where the breakpoint code has been called and have experienced the same result.
Im using 64bit Win7 -
JDK - 1.7.0 update 40
Output:
LOAD TIME : 329UsersCache.fillIn() time = 4 ret==null?: true
UsersCache.fillIn() time = 3 ret==null?: true
tableAlias.cardinality()==0
UsersCache.fillIn() time = 4 ret==null?: true
UsersCache.fillIn() time = 3 ret==null?: true
tableAlias.cardinality()==0
UsersCache.fillIn() time = 4 ret==null?: true
tableAlias.cardinality()==0
tableAlias.cardinality()==0
tableAlias.cardinality()==0
Debugger Output:
Connecting to the database Layout Pro.
Executing PL/SQL: ALTER SESSION SET PLSQL_DEBUG=TRUE
Executing PL/SQL: CALL DBMS_DEBUG_JDWP.CONNECT_TCP( '*****', '*****' )
Debugger accepted connection from database on port *****.
Executing PL/SQL: CALL DBMS_DEBUG_JDWP.DISCONNECT()
Process exited.
Disconnecting from the database Layout Pro.
Debugger disconnected from database.
Thanks in advance,
James

Hi
Have you compiled for debug? - Yes
Are the breakpoints definitely on code lines?- There are several lines of code which have up to 5 consecutive breakpoints
You can also set the preference Tools| Preferences|Debugger|Start Debugging Option to 'Step Into'. That should stop at the first executable line. - This worked thank you, I can now access the debugger and test my work.
On swapping the preferences back to 'Run Until a Breakpoint Occurs' (which it was originally set as) the debugger now correctly stops a the breakpoints. I didn't make any changes to the code/debugger parameters or anything so I'm rather confused to why its suddenly started working .
But anyway thank you for the help,
James

Debugger starts allways one times

Hi
I have read many hours and many articles but i cannot find the problem. I think it is with the Ports but for me it seems that all settings are correct.
In CF Administrator is Port 5005 and Line Debug is activated. The JVM Arguments are as decriped in many articles and in the help. The Firewall does not blocks Port 5005 (and I have tried with deactivated).
I can start the debug in CF Builder one time only correctly. When I will start a second time the debugger hangs and says cannot connect to RDS Server, (Unable to connectto RDS Server) but the RDS runs correctly as I can see in my databases, RDS Dataview shows all databases correctly at the same time.
I am greatfull for any ideas.
Regards Roger

Yes CF9 with Update 9.0.1, Standalone on Win64 with IIS. Istalled on the default locations.
According to your questions I came to the solution that the problem was in CF server and not in CF Builder. I have completely deinstalled and reinstalled the CF server and it works well now.
Thank you for your assistance I am happy.

Last line is still not read

Hi,
I fixed error in last post and rewrote the code using ProcessBuilder instead.
Output from my unix tool is:
Command is a shell application' /home/myid/test/myshell/bin/run' that starts a ascii gui that looks like ( see below). It waits for input from user.
*   My shell Application                   *
HELP: h
COMMAND: c
QUIT:q
135.19.45.18>
And still the last line is not showing when I read the text.
I have tried with readLine() and I get the same error.
Note: When I debug, after characters in line:
OUIT:q
have been read I can see that debugger hangs on
br.read()
And now the code looks like:
import java.io.BufferedReader;
import java.io.BufferedWriter;
import java.io.IOException;
import java.io.InputStream;
import java.io.InputStreamReader;
import java.io.OutputStream;
import java.util.ArrayList;
import java.util.List;
public class RunShellCmd {
    private BufferedReader processInputStream;
    private BufferedWriter processWriter;
    public static void main(String args[]) throws Exception {
        RunShellCmd cmd = new RunShellCmd();
        cmd.runCmd();
    public void runCmd() throws Exception {
        Process process = null;
        List<String> cmd = new ArrayList<String>();
        cmd.add("/bin/bash");
        cmd.add("/home/myid/test/myshell/bin/run");
        ProcessBuilder processBuilder = new ProcessBuilder(cmd);
        processBuilder.redirectErrorStream(true);
        try {
            System.out.println("start process ....");
            process = processBuilder.start();
            InputStream is = process.getInputStream();
            InputStreamReader isr = new InputStreamReader(is);
            BufferedReader br = new BufferedReader(isr);
            StringBuilder sb = new StringBuilder();
            int intch;
            while ((intch = br.read()) != -1) {
              char ch = (char) intch;
              sb.append(ch);
              System.out.println(sb.toString());
        } catch (IOException e) {
            System.out
                    .println("An error occourd: "
                            + e.toString());
        } finally {
            processInputStream.close();
            process.destroy();
            System.out.println("exit value: " + process.exitValue());
            processWriter.close();

DUPLICATE THREAD!
Please don't create duplicate threads. You already have a thread for this same issue.
I fixed error in last post and rewrote the code using ProcessBuilder instead.
Good - then post your progress in the original thread and keep using it until the problem is resolved. That way the people that tried to help you before can see the entire context of what you are trying.
https://forums.oracle.com/thread/2611844

Jdeveloper 11.1.1.4 Could not create MAR entry for file

Hi
i am using jdev 11.1.1.4.i checkout code from svn to jdeveloper .
i tried to create EAR file for the application,but while creating EAR jdeveloper throwing some error message as shown below
find similar thread
JDeveloper Debugger Hangs
Could not create MAR entry for file [D:\JDeveloper\mywork\myAPortalApp\Portal\adfmsrc\oracle\webcenter\portalapp\pagetemplates\.svn\text-base\pageTemplate_swooshyPageDef.xml.svn-base], due to: MDS-01161: Reference "/oracle/webcenter/portalapp/pagetemplates/.svn/text-base/pageTemplate_swooshyPageDef.xml.svn-base" has an invalid character ".".
from the above message ,due to svn in the output folder ,jdeveloper is not able create MAR file entry .
i checked application properties for filter options ,jdeveloper has already has the filter "Exclude /.svn/"
can any one help me on this?
appreciate your help

Hi Aaron thanx for the reply.
i did not understand exporting from the subversion,but i did search in file for the svn there are two entires for .svn in portal.jpr file.
if i delete subversion connection from the jdeveloper and if i compile then it will create EAR file.

CVI2013 crashes when using .dll on *some* computers

So I have made a .dll in LabVIEW that I inted to use in CVI (you can reference this thread for some additional info about it) and it worked just fine on the computer I created it on. Trouble started when I began testing it on other machines. A little background of my set up might be helpful so here it is. I work in a HIL lab and we have a few different test setups including NI, dSPACE, and some proprietary testers. We use CVI to run test scripts and this .dll is used to control relays via USB.
The issue I am seeing is something I haven't seen before and am somewhat clueless as how to debug - I think it potentially could be a CVI problem. When this .dll and .lib are added to my project and I set a break point, everything seems to work fine. I step through my code and everyone runs as expected (.dll related functions as well as any other part of the program), but as soon as I hit the "Continue" button or the "Go to Cursor" button CVI freezes and subseqently crashes. The debug .exe stays open (but crashed) and I can't kill the process with Windows - I eventually have to restart the computer. My program will run just fine without break points and will let me step through to the end of the program if I have already set a break point.
I have run the same exact project on multiple computers and so far it has only happened with computer that have dSPACE/Matlab software insalled. I'm not sure if that is significant (it shouldn't make a difference) but it's another detail to report. I have tried CVI2013 SP2 on one of the dSPACE computers and that did not help (the rest of the computers still have SP1).
I've also looked through my LabVIEW .dll build settings, made adjustments, and rebuilt to see if that would help and it has had no effect.
Any input, direction, advice, etc. would be helpful. I'm stumped. Thanks in advance.

Can you try WebBrowser example(samples\userint\activex\WebBrowser.csw) to see if the debugger hangs?
Put a breakpoint for example on Refresh() callback. Run the program and push the refresh button, the breakpoint should be hit. See if continuing execution the hang happens.
Do you use TeamViewer on the computer you see the hang(see this reply)?
Other than that I have no other ideas.
Constantin

Debugger hangs

Similar Messages

Maybe you are looking for