I am puzzled: when I am running EPIC Perl debugging tool it produces "Timed out while waiting for Perl debugger connection" error along with "Unable to connect to remote host: 192.168.1.37:5000
Compilation failed in require...." on the console.
I am on OS X 10.11.1 (El Capitan, darwin 15.0), using Eclipse Kepler 4.3.2, EPIC 0.7.0 (same thing happens with 6.5.6), and Perl 5.18 (prebuilt for darwin) or ActiveState Perl 5.20
Do you have any suggestions?
Thanks in advance.
It looks like I found the answer. The IP address mentioned in the error message is the one that I had statically added in the hosts file. For some reasons EPIC searches this address for debugger connection skipping dynamic addressing assigned by DHCP.
Related
I'm running PyDev 6.4.1.2 on Eclipse EE Neon (4.6.3) on OS X 10.11.6 (El Capitan)
Whenever I update the PYTHONPATH and syncing is attempted, I get 3 warnings that Python has crashed. The updated PYTHONPATH still works, but I was wondering what the possible cause of this could be.
Thank you.
The reason it crashes is because when doing some_module = __import__("some.module"), dir(some_module), that module is crashing and usually means an error in compilation of such module or some wrong environment variable (so, the module is not being properly initialized).
I'm not sure PyDev prints which module was the culprit... do you have some error in your error log after the crash happens?
http://www.pydev.org/faq.html#HowdoIReportaBUG has instructions on finding the error log.
We're getting ready to deploy our application (Cytoscape) for Windows, Linux and Mac.
We find that when Java 9 is installed on Fedora 26 64 bit, trying to run the installer gives "JVM must be greater than 1.6", though our JVM range is set to 1.8.0_152...1.9.
Is there a later installer/launcher version that gives a more informative error message? ... could we have something misconfigured??
On the same platform, but with Java 10 installed instead, the launcher apparently allows execution to commence (despite our JVM range). This ends badly, as Karaf complains:
/opt/Cytoscape_v3.6.1/framework/bin/karaf: line 242: [: : integer expression expected
-Djava.endorsed.dirs=/usr/java/jdk-10/jre/lib/endorsed:/usr/java/jdk-10/lib/endorsed:/opt/Cytoscape_v3.6.1/framework/lib/endorsed is not supported. Endorsed standards and standalone APIs
in modular form will be supported via the concept of upgradeable modules.
Error: Could not create the Java Virtual Machine.
Error: A fatal exceThe programmes occurred. Program will exit.
Is the launcher somehow misidentifying the JVM? Shouldn't it give an informative error and stop the launch (including Karaf) from proceeding?
Thanks!
I just installed CUDA 5.0 Preview (Mac OS X Lion) and I'm having trouble with Nsight.
The toolkit seems to be installed correctly. (Driver loads, nvcc -V works in bash, samples work fine).
When I create a new project I get warnings:
Error launching external scanner info generator (nvcc -dryrun ...)
Program 'nvcc' is not found in $PATH
In Preferences -> CUDA Toolkit I get no CUDA-compatible devices detected. Which is strange because I have nVidia GT 650M on my machine. So why doesn't Nsight recognize it?
If I try to build a project I get 2 errors:
/bin/sh: nvcc: command not found
make: * [src/test.o] Error 127
How do you start Nsight? Do you use /usr/local/cuda/bin/nsight? Unfortunately, it is not currently possible to launch Nsight by double-clinking the application on Mac OS X.
In the CUDA 5.0 Preview build we had a bug when shell script did not properly setup paths. This is how this script looks like in latest internal toolkit builds (you may need to adjust paths depending on your toolkit install location - in the final release installer will handle it):
#!/bin/sh
PATH="$PATH:/Developer/NVIDIA/CUDA-5.0/bin" DYLD_LIBRARY_PATH="$DYLD_LIBRARY_PATH:/Developer/NVIDIA/CUDA-5.0/lib" "/Developer/NVIDIA/CUDA-5.0/libnsight/nsight.app/Contents/MacOS/nsight" $#
I'm n00b to NDK
I used instruction from http://wiki.eclipse.org/Sequoyah
I'm using:
Eclipse: 3.7.2
NDK: r7b
Platform tools: 10
tools: 16
Sequoyah: http://download.eclipse.org/sequoyah/updates/2.0/
I'm just trying to debug hell-jni sample which comes with ndk, aim is to switch between java and C/C++, and debug both native and java code.
I'm getting error: Connection reset by peer.
This is because the eclipse will start the gdb server, on the other hand, the ndk-gdb script will start the gdb server.
Solution is to find the ndk-gdb in your ndk dir, and comment out the last line
like this: ## $GDBCLIENT -x native_path $GDBSETUP save and it should be OK.
or copy/paste the ndk-gdb to ndk-gdb-eclipse, and make the same changes in ndk-gdb-eclipse, and tell eclipse to start gdb server using ndk-gdb-eclipse, via some portal in Debug Configurations=>C/C++ .
I had this working fine until today and I have seemingly tried everything. I get an error when I try to launch a debugger in eclipse with PTP on OSX. The error comes up as:
Error completing debug job launch
Reason: Debugger error: Unable to
determine gdb version
I have tried running the same code in regular debugger, minus all the MPI stuff and that works fine. It also works fine when I simply run the MPI job locally. I have read somewhere that this might be an issue with Process Launcher? Where do I check this in PTP? I am also using latest Indigo eclipse with PTP version 5.0 and I have also built the sdm ddebugger for mac locally.
This also appears in console:
gdb: invalid option -- q
sdm [--debugger=value] [--debugger_path=path]
[--proxy=proxy]
[--ho
st=host_name] [--port=port]
[--master]
[--server=rank]
[--debug[=level]]
Finally, running gdb from terminal gives me:
GNU gdb 6.3.50-20050815 (Apple version
gdb-1515) (Sat Jan 15 08:33:48 UTC
2011)
Any ideas?
Thanks, Alex