[Oorexx-devel] Question ad compiler output for debugging

2009-05-25 Thread Rony G. Flatscher
Currently, whenever I run into an exception under the control of Java, the MSVS2008 Professional debugger does not get triggered, instead a file hs*.log gets created with all sort of interesting information. Eg. (this one is from pressing Ctl-c in a hanging ooRexx program, that got started via

Re: [Oorexx-devel] Question ad compiler output for debugging

2009-05-25 Thread Rony G. Flatscher
Rick McGuire wrote: Have you tried building a a debug vsrsion of ooRexx to run with? If you're running from an installed version, build the debug version and drop the new .exes and dlls in the install location, along with the .pdb files containing the debug symbols. Yes, I always build

Re: [Oorexx-devel] Question ad compiler output for debugging

2009-05-25 Thread Rick McGuire
Just building a debug version of the install package is not enough. You also need to place the symbols files in the same directory so the debugger can find the symbols. Everything you've shown so far suggests the symbol files are getting located. Rick On Mon, May 25, 2009 at 3:13 PM, Rony G.

Re: [Oorexx-devel] Question ad compiler output for debugging

2009-05-25 Thread Jean-Louis Faucher
Rony, Since you have EXCEPTION_ACCESS_VIOLATION (0xc005) you can try to select the Access violation in Debug / Exceptions, under Win32 exceptions. See http://msdn.microsoft.com/en-us/library/d14azbfh.aspx It's written : The debugger can break execution of your application immediately when

Re: [Oorexx-devel] Question ad compiler output for debugging

2009-05-25 Thread Rony G. Flatscher
Jean-Louis, Since you have EXCEPTION_ACCESS_VIOLATION (0xc005) you can try to select the Access violation in Debug / Exceptions, under Win32 exceptions. See http://msdn.microsoft.com/en-us/library/d14azbfh.aspx It's written : The debugger can break execution of your application