I just installed Netbeans 7.1.2 on a system. It all installed well. However, when I try loading the IDE it starts briefly and only to exit after a while at the usual "Loading Cached Objects". Any form of help to tackle this will be appreciated.
The Output from the console :
The launcher has determined that the parent process has a
console and will reuse it for its own console output:
Closing the console will result in termination of the running program
Use '--console supprress' to suppress console output
Use '--console new' to create a separate window
Java HotSpot<TM> 64-Bit Server VM warning : ignoring option
PermSize=32m; support was removed in 8.0
Java HotSpot<TM> 64-Bit Server VM warning : ignoring option
PermSize=32m; support was removed in 8.0
Then it terminates
Related
I am running Homestead on Windows 10 machine with Virtual Box. I have VSCode running on the Windows machine and I want to be able to debug code in the VM.
I have followed this setup:
https://tighten.co/blog/debugging-configure-xdebug-and-laravel-homestead-and-vs-code-and-phpunit
Once I am listening for Xdebug I run my code in the VM using phpunit test/Feature/AdminTest.php and this fails with
Unable to open 'BaseTestRunner.php': File not found
(file:///c:/g/Sites/Laravel/everyone-in-mind/vendor/phpunit/phpunit/src/Runner/BaseTestRunner.php).
Which is obviously showing me the Windows path.
If I stop the debugger and run again the test runs fine.
Do I need to install something extra to get BaseTestRunner?
When you are debuging a PHPUnittest with xDebug in VSCode with the PHPUnit plugin from Elon Mallin, check that you have disable the option Breakpoints/Everything.
It seems as if PHPUnittest, running from the PHPUnit-plugin, could not find the BaseTestRunner.php file and raised an exection. When you ignore this exception, you can run and debug your test.
see the same question PHpUnit with xdebug Breaks at BaseTestRunner instead of the actual test
It works for me and can now debug the Unittest.
I recently started developing for Node.js/Express with Nodeclipse. I added a run configuration for package.json with goal start. This works as expected, the start command from package.json is executed (node ./bin/www). I can see this command in Eclipse's console view and I can see two node.exe processes appear in Windows Task-Manager. HTTP requests to http://localhost:3000/ are logged in the console.
However, klicking the red "Terminate"-Button in Eclipse's console view leaves the node.exe processes running. Subsequent attempts to start the app fail because the port is already in use.
I do not have this problem when I start the app with npm start in Windows cmd. Stopping the execution with Ctrl+C will also exit the node.exe processes.
This is my IDE-Setup:
Eclipse Luna SR2 (4.4.2) under Windows 7 x64 with jre1.8.0_45
Eclipse was setup this way: extracted eclipse-platform-4.4.2-win32-x86_64.zip (from here), installed Eclipse Marketplace Client, then installed Nodeclipse via Drag&Drop from nodeclipse.org
Node.js version v0.12.2 (for Windows x64)
express-generator (version 4.12.1) is installed globally
How can I make the Terminate button in the console view actually terminating the node.exe processes?
It seems that Eclipse only kills the npm script that is used to start up node. The thing is that Eclipse forcibly kills that script, giving it no chance to send any signals to the node.exe process.
This bug explains why this works this way.
Step 1:
Run command-line as an Administrator. Then run the below mention command. type your port number in yourPortNumber
netstat -ano | findstr :yourPortNumber
Red coloured circled area shows the PID (process identifier)
Step 2 :
Then you execute this command after identify the PID.
taskkill /PID typeyourPIDhere /F
P.S. Run the first command again to check if process is still available or not. You'll get empty line if process is successfully ended.
I am using Eclipse 4.4 and Pydev 3.7.
When I create the console type "jython using VM running eclipse console" and then close the console, Eclipse exits. I don't see any errors or messages, it just shuts down. Is this the expected behavior? I don't recall seeing it work this way before. This doesn't happen with the Jython or Python consoles.
Is anybody else seeing this?
Yes it happens to me too when I close it except I do get an error message :
If I were you I wouldn't worry about it too much. For consoles I prefer using the command prompt instead.
When I do on my app.js Debug As > Node Application it says
Launching STANDALONE_V8 has encountered a problem.
Failed to connect to Standalone V8 VM
connect timed out
It should start an app. Doing so directly on my terminal works fine.
When I start a debug session in my terminal and than try to debug it in Eclipse works fine too.
So is there anything that has to be done in order to make it work in Eclipse?
What exact error is in ErrorLog View on in Nodeclipse Console?
What is Java is used and Nodeclipse version?
Try to specify Java version: in eclipse.ini point to JDK 7
Check also
- toggleBreakpointsTargetFactory specified id is already registered
I'm runnung Eclipse (indigo) 3.7.1 with Xdebug 2.1.3 on Ubuntu 10.04 LTS, PHP 5.3.2-1ubuntu4.14.
My problem: While debugging Drupal installation everything works fine, adding breakpoints, stepping in, over, return, vars are showing as they suppose to. But, once the execution flow takes me to the other file which holds the definition of a function being called in the first file, I get an error message saying: "Unexpected termination of script. Debugging ended.".
Show super global vars is switched off in Xdebugger options (solution I found previously), and 'Path Mapper' is left blank in PHP server options (another solution).