I already know how to change the version of the Lua interpreter by going to the menu-option
"Project -> Lua Interpreter".
I see the confirmation by executing a Lua-file containing the line print(_VERSION), which outputs the set version e.g. Lua 5.3.
However, when I type _VERSION into the "Local console" I still get "Lua 5.1".
Any advice on how to change the Lua version of the local console as well?
The Local console uses the same interpreter that runs the IDE itself, so it's not possible to change at this time. There is a ticket open that could enable support for other Lua versions, but it hasn't been implemented yet.
As a simple workaround you can start normal/remote debugging with the selected interpreter (Lua 5.3, for example) and run all the commands you need in that environment (in the Remote Console).
Related
I'm having problems running the FreePascal IDE (for Win32 for i386) Version 1.0.12 2011/04/23 Compiler Version 2.4.4. It crashes when I want to "Open" and "Save as"
When I select one of those options in the Menu the IDE returns: "Program generated a RTE 215 at address $00696A49" which prompts me to close the IDE, and then shows three addresses in a separate window: $00696A49 and 2 others (random).
If you need to know, I have been loading .pas files from directories other than FP's own, and the IDE used to show "couldn't load file from current directory"-like messages.
I want to know what's generating this problem and if I have to update it.
Thanks in advance.
Despite 2.4.4 being an older release, it shouldn't happen with a win32 release in normal situations (like on harddisk, not network drive, no special permissions in sight).
You could try using a different system and see if it fails there too, or try a newer version.
I see there is a project named spark, which is a Chrome app based development environment.
It seems interesting, and I want to run it my own computer(mac os), expected to see a chrome-based IDE for dart. But I can't find any document to tell me how to run it. There are just some pages for how to develop and test, but how to run it?
I tried with the grind shell with all kinds of options, but no lucky :(
Thanks for the question! The Spark effort is still spinning up, and we're not yet ready for a public release. All the source code is available publicly, so it is possible for people to build it for themselves. Once we're further along we'll put a developer preview release up on the chrome web store.
The steps to build & run Spark IDE on Windows are:
Install Dart SDK to e.g. C:\dart-sdk
Download the Spark source code to e.g. C:\spark
Open cmd and type: cd C:\Spark
set PATH=%PATH%;C:\dart-sdk\bin
set DART_SDK=C:\dart-sdk
pub get
grind.cmd deploy
Load the upacked extension from C:\Spark\ide\build\deploy-out\web in Chrome Dev.
Alternatively, you can download Chrome Dev Editor packaged app, based on Spark 0.13,
I am trying to install some commercial software that was written in Java for a Windows computer operating system. I have downloaded Java from their site and I have also downloaded the JDK package for a 64bit windows system so to my knowledge I should have everything I need to have java work. I then create a shortcut of the java exectuable javaw.exe and edit the target path and the start in path to my specifications but when I go to execute it, it tells me that it "Could not create Java virtual machine".
Does anyone know how to fix this error?
Luke H
How are you creating the shortcut? In windows, this might not be the correct approach.
Does the installer use an embedded version of java? It is possible that the software uses some native libraries that aren't compatible with 64 bit java.
Depending on the setup script, it may be passing invalid command line arguments to the version of Java you installed.
Its a bit late, but this might help others later.
Here's what worked for me:
Target: "C:\Program Files\Java\jre1.7.0\bin\javaw.exe" -classpath C:\OLINDA olinda
Start in: C:\OLINDA
It seems that you don't know how properly start the Java Virtual Machine, in Windows, the JVM can be started with two executables one is java.exe and the other one is javaw.exe, both do the same, the only difference is that java.exe is a command line tool (so you'll see a command line when you start your application) and javaw.exe simply omits the command line. Both use the same paramaters that can be found here: http://docs.oracle.com/javase/1.5.0/docs/tooldocs/windows/java.html, from this the shorter way to open a Java program will be:
java MainJavaClass.class
or
java -jar JavaProgram.jar
Most commercial programs are packed in jar files so probably you will use the second approach, but also be warned that usually commercial Java programs use a native wrapper so you can simply launch a native application (in Windows .exe), without the need to set anything, so you may need to create a shortcut for it instead of the java.exe program, in the case you really need to call the Java program through the JVM, then what you need to change is the Target field so you include the parameters you need to pass to it like this:
"C:\Program Files\Java\jre7\bin\java.exe -jar JavaProgram.jar"
Another way could be use a batch file to start the program and create a link to it instead.
We have our code and binaries in Unix box .Few of the binaries are for web packages loaded by CGI .I use gdb in remote debugging mode to debug normal binaries but web binaries are difficult to debug because the process id changes every time the binary is loaded and gdb detaches .I heard in Visual studio there is a option to add in task manager and debug it .But i m afraid if i install Visual studio my system would go slow.Any suggestion on any other opensource tools available for efficient remote debugging of web binaries
The best thing you can do is to efactor the code so you can test most parts of it outside a CGI context with some unit testing system or something similar.
The second step would be to replay the CGI communication manually. It's not complicated - set the environment variables needed and eventuelly pipe the POST data in while running under gdb.
If that doesen't help you have to debug the web server and ask your debugger to follow child processes. Best thing is to start the httpd using the -X option so it runs with a single process itself. Then attach gdb and set the set follow-fork-mode child command. See gdb manual at http://sourceware.org/gdb/onlinedocs/gdb/Forks.html
I downloaded and installed the latest version (6.12.2.633) of Debugging tools for windows. Running it with .NET 4.0. When I run !address -summary command seem like its output is different than what I used to see with previous version of Windbg/SOS for .NET 3.5. Anyone knows where can I find document for latest !address -summary command. SOS build-in help is not very helpful
!address is a native extension command that is always available during user mode or kernel mode debugging. It displays information about the memory of the target application or computer. See also the documentation for this command.
It is possible to have multiple extensions loaded in WinDbg. You can use the .chain command to list the loaded extensions.
SOS is an extension dedicated to .NET debugging. It comes with its own set of commands to analyse memory used by managed applications, e.g. !eeheap -gc.