Jump to content
Excelsior Forums


Excelsior Staff
  • Content count

  • Joined

  • Last visited

Everything posted by zztop

  1. Release date of Excelsior JET 6.5

    Well, it took a little bit more time... Today is June 15th and Excelsior JET 6.5 is here.
  2. Excelsior JET 6.5 is out

    We are pleased to announce that Excelsior JET 6.5 is now available! The major new feature included in this release is a protected environment for running Eclipse RCP applications. Check what our customers say about this new capability. The full list of improvements in version 6.5 is available on the what's new page.
  3. Erro Compile test.c for Call DLL

    C:\jet6.4-eval\samples\Invocation\cMain contains build.bat that starts with @set jdkdir= Specify the path to a JDK installation on you machine. You could find the build instructions in the file C:\jet6.4-eval\samples\Invocation\cMain\readme.txt
  4. Problem Dll Excelsior

    That sounds much better. Please check the sample <JET Home>\samples\Invocation\cMain which illustrates how to invoke Java code from a C program.
  5. Please contact Excelsior Support Dept. (java at excelsior-usa.com)
  6. Problem Dll Excelsior

    Please clarify what you mean. I ain't sure I understand what is the problem.
  7. Release date of Excelsior JET 6.5

    We have 1.5 week before the end of May.
  8. 64 bit JET

    Unfortunately, the size of L1, L2,L3 cache (which is often crucial for performance) is NOT doubled in the 64-bit mode. And more data are actually read from memory due to alignment requirements and using 64-bit pointers thus inreasing pressure on the memory subsystem (the known "short pointers" optimization is not silver bullet) This degradation was observed on both .NET runtime and Sun HotSpot when running the same tests on the same machine in 32- and 64-bit mode. Of course, that appears not for all applications. In general, the main value of 64-bit systems is breaking the 4GB address space limit. Basically, that's true for (integer) number crucnhing apps and the like due to a larger number of CPU registers.
  9. 64 bit JET

    It's clear. We will notify you as soon as the first beta with support for x64 is available.
  10. I guess many customers changed their code to use Application Data instead of Program Files.
  11. 64 bit JET

    Of course, we have such plans and we have been already working on 64-bit version of Excelsior JET about a year (it's a huge task). At this time, I cannot publish any release dates, though. Be prepared that pefromance may degrade on 64-bit platfrom due to some memory overheads (e.g. if you compare performance of your application on the same computer). Did you compare performance when using 32-bit and 64-bit JRE on the same computer?
  12. Yes. The latest Windows security policies do not to allow apps to create files in subfolders of Program Files. That's not about Excelsior JET. You need to change your code to store output files in another location.
  13. Yes, it's enough if you set your own Java system property in JetPackII as -Dmy.property=$(Root) and then get the value of "my.property" in the program. The next question is if the problem appears when the application is installed into a separate directory, say in "C:\MyApp" not in <system drive>\"Program Files"?
  14. Does the problem appear right after compilation or after deployment with JetPackII? Is it possible to reproduce it with the latest Excelsior JET 6.4? You must mean Excelsior JET 4.1 released back in 2005. Note that according to the Support Policy statement Excelsior JET 4.1 has reached Product End Of Life status. We encourage customers of this version to migrate to more recent versions to receive the support services under valid Support Contracts. If you need help in migrating to a newer version of Excelsior JET, please contact us.
  15. How do you determine the working directory in the application code? Do you use a Java system property, OS env. variable, or something else?
  16. Excelsior JET 6.5 Beta 5

    Excelsior JET 6.5 beta 5 concludes the long beta testing period started on August 1st 2008, the day of the total solar eclipse. Since version 6.5, Excelsior JET will become the most secure environment for running Eclipse RCP applications. The major improvement over previous beta versions is a significant reduction of JIT compilation time. The full list of improvements in Beta 5 is available on the download page.
  17. reverse engineering

    Actually, it's harder because the tools for re-engineering C++ code often rely on the code patterns produced by the widely used compilers like MSVC, GNU, Borland Power Builder, etc to partially automate the process.
  18. New to Excelsior

    Hi Bobby, I guess you mean native method libraries under "resources such as dll's". For this scenario, Excelsior JET compiles jar files to the executable and remains native method libraries as is. No changes in the sources code are necessary to make it work.
  19. No Stack Trace and Error Diagnosis

    You may compile your application with stack trace disabled. When stack trace is necessary, run the executable with the following script ---------- run.bat SET JETVMPROP=-Djet.stack.trace YourApp.exe ----------
  20. Compiled Program runs in an infinite loop

    Hotfix is on the way (sent to your Technical Contact)
  21. Does it mean that the bug lurks in Excelsior JET? Not necessarily... Continued in this Excelsior's blog post.
  22. Unrecoverable errors are those preventing the program from further execution, that is, the errors (crashes) which cannot be handled. A known example is access violation that occurs when reading/writing memory at an address to which no memory page was mapped or transferring control to such a region. If a JET-compiled application runs into the problem, the Runtime prints TRAP#3 message and execution abnormally terminates. Of course, it should never happen in a pure Java application but, unfortunately, it may happen due to: bugs in the native method libraries used by the application JNI misuses (correct usage of JNI is tricky for inexperienced programmers) operating system malfunction (yes, we found a few examples when debugging) bugs in the JET Optimizer or Runtime (despite it?s a rare case for the matured versions released last years, we must be honest with you ) Often, the errors are volatile, that is, hardly reproducible. I recall a support case when an Excelsior JET customer received reports about an unrecoverable error from his customers but he could not reproduce it in his test environment. Of course, he was not able to provide Excelsior Support with a sample on which the problem appeared. After many trilas we finally managed to find the root cause but it was double tough. To address the problem, we scheduled implementing a special diagnostic facility in Excelsior JET 6.5. If an unrecoverable error occurs, the JET Runtime collects various information about the application state, logs it into a file, and prints the error message referencing that file. We believe this feature will enable us to reveal the root cause of the errors faster and easier and help our customers. The diagnostic logging has been already implemented and is available in Excelsior JET 6.5 beta 4.
  23. Diagnostics of unrecoverable errors

    Exact dates may vary May 2009 would be a more realistic estimate
  24. How do I generate multiple updates to the same version?

    I confirm that all updates can be built automatically. Particular instructions depend on how your current build is organized. I mean did you create new installation packages for version 1.5 and 1.6 or the packages were updates to version 1.0?
  25. How do I build installer updates from the commandline?

    Yes, the result should be the same provided the files you added to the update project are not changed. JetPackII projects contain only full path references to the included files so if the physical files are modified since the previous build, the resulting package changes as well.