|
|
Right Java tools for J2EE, Web Service, Grid and more |
| |Home | Products | Documents | Downloads | Purchase | Support | Company | Partners | Contact | |
FAQ For LimpidDebugger
General
Will LimpidDebugger replace traditional debugger?
No. LimpidDebugger will never be as convenient as regular debuggers, because LimpidLog-LimpidDebugger is a two-phases log-debug process. LimpidDebugger is useful and powerful when a traditional debugger can not be used. For example, if you have a J2EE application running on production at a remote data center, you can not run your application under your debugger. You can not set break points. In that situation, LimpidDebugger is useful and very powerful. It is a must. LimpidDebugger will replace traditional log and trace.
Do I need runtime environment to use LimpidDebugger?
No. LimpidDebugger re-plays the historical data which was recorded at runtime by LimpidLog. Your runtime environment (environment variable, libraries, application servers, ...) are not needed.
LimpidDebugger does go line by line in the correct order, but no local variable information. Why?
Your application was not compiled use -g option. There is not enough debug information in your class file. For LimpidDebugger, the more debug information the better.