[Oorexx-devel] rxapi abends ...
After porting a dbus language binding for ooRexx to Windows XP and running some testscripts, a situation arises where rxapi abends. The scenario: * ooRexx 4.1.0, 32-bit * the testscript starts a private dbus which creates a server socket and listens to clients (address used by dbus to setup the server: tcp:host=localhost,port=23000,family=ipv4;) o after the testscript ends normally a trap occurs and popup is shown (querying whether to send the information to MS) As setting up the environment is currently complicated, first the question, whether there is something I can/should do to narrow down the possible causeß (The gut-feeling says that it has to do with shutting down the server socket by dbus, which may interfere with rxapi on Windows. The very same testscripts run flawlessly on Linux and MacOSX.) ---rony -- Get a FREE DOWNLOAD! and learn more about uberSVN rich system, user administration capabilities and model configuration. Take the hassle out of deploying and managing Subversion and the tools developers use with it. http://p.sf.net/sfu/wandisco-d2d-2___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] rxapi abends ...
Thank you very much, Jean-Louis! (Had hoped there were alternatives before that due to overcommitted time-resources. E.g. took me more than two days to get the Windows version to compile and link successfully! Had to remove the /Gr switch from the MS compiler.) O.K., then one more question: is there a 32-bit debug version of ooRexx available somewhere that I should/could use? If not, then for which version of ooRexx should I create a debug version: from the trunk, from the 4.1.1 branch or from 4.1.0 ? ---rony On 20.08.2011 14:41, Jean-Louis Faucher wrote: Assuming : - you don't have just-in-time debugging (I don't have it with VC express 2010) - you can open a cmd shell in which your environment is set (path, classpath, environment variables, ...) - you use a debug version of oorexx 4.1.0 - you use a debug version of dbus then I would do that : from your cmd shell, type : C:\Program Files\Microsoft Visual Studio 10.0\VC\vcvarsall.bat x86 (adjust to your config) then launch vcexpress : vcexpress /useenv then open or create a VC++ project then edit the debugging properties of the project. Idon't know which commands you start, below is an example for a .bat file. command = cmd /c command arguments = my_script.bat working directory = my_dir then debug/start debugging (F5) when the crash occurs, you should have the call stack. If the executable which crashes is on the server side, then it's this remote executable that you must launch from VC Express. In this case you may need to separate your script in two parts : - the client part - the server part If this is rxapi which crashes, then follow the procedure above, by setting command = my_path_to/rxapi.exe (don't forget to kill rxapi before) then run your script. Jean-Louis 2011/8/20 Rony G. Flatscher rony.flatsc...@wu-wien.ac.at mailto:rony.flatsc...@wu-wien.ac.at After porting a dbus language binding for ooRexx to Windows XP and running some testscripts, a situation arises where rxapi abends. The scenario: * ooRexx 4.1.0, 32-bit * the testscript starts a private dbus which creates a server socket and listens to clients (address used by dbus to setup the server: tcp:host=localhost,port=23000,family=ipv4;) o after the testscript ends normally a trap occurs and popup is shown (querying whether to send the information to MS) As setting up the environment is currently complicated, first the question, whether there is something I can/should do to narrow down the possible causeß (The gut-feeling says that it has to do with shutting down the server socket by dbus, which may interfere with rxapi on Windows. The very same testscripts run flawlessly on Linux and MacOSX.) ---rony -- Get a FREE DOWNLOAD! and learn more about uberSVN rich system, user administration capabilities and model configuration. Take the hassle out of deploying and managing Subversion and the tools developers use with it. http://p.sf.net/sfu/wandisco-d2d-2___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] rxapi abends ...
O.K., then one more question: is there a 32-bit debug version of ooRexx available somewhere that I should/could use? If not, then for which version of ooRexx should I create a debug version: from the trunk, from the 4.1.1 branch or from 4.1.0 ? Well, I think you should definitively build your own debug version :-) Use the version you plan to use for dbus (4.1.0). I assume you know what to do :-) Jean-Louis -- Get a FREE DOWNLOAD! and learn more about uberSVN rich system, user administration capabilities and model configuration. Take the hassle out of deploying and managing Subversion and the tools developers use with it. http://p.sf.net/sfu/wandisco-d2d-2___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] rxapi abends ...
You probably have already all what needed to build several versions of ooRexx. But just in case, I attached files which set environment for 4.1.0 and main (adjust to your own paths). This is a simplified version of the scripts I use, but they are enough to build/test. When you double-clic on one of them (after renaming .txt to .bat), a cmd shell is opened. Enter : cdtrunk makeorx DEBUG From here, you can test your scripts. Jean-Louis set config=dbg set src_drv=d: set oorexx_dir=\local\Rexx\ooRexx set src_dir=%oorexx_dir%\svn\main\releases\4.1.0\trunk set doc_dir=%oorexx_dir%\svn\docs\releases\4.1.0 doskey cdtrunk=%src_drv%$Tcd %src_dir% echo Setting path for running ooRexx ^(%config%^) set PATH=%src_drv%%src_dir%\Win32%config%;%PATH% echo Setting path for killer.exe set PATH=%src_drv%%oorexx_dir%\ooRexx-build-utils-1.0.0-windows;%PATH% call E:\Program Files\Microsoft Visual Studio 10.0\VC\vcvarsall.bat x86 set MSVCVER=9.0 set PATH=D:\XSLT\Xalan-C_1_10_0\bin;%PATH% %comspec% /k title Environment for ooRexx-4.1.0 (%config%) set config=dbg set src_drv=d: set oorexx_dir=\local\Rexx\ooRexx set src_dir=%oorexx_dir%\svn\main\trunk set doc_dir=%oorexx_dir%\svn\docs doskey cdtrunk=%src_drv%$Tcd %src_dir% echo Setting path for running ooRexx ^(%config%^) set PATH=%src_drv%%src_dir%\Win32%config%;%PATH% echo Setting path for killer.exe set PATH=%src_drv%%oorexx_dir%\ooRexx-build-utils-1.0.0-windows;%PATH% call E:\Program Files\Microsoft Visual Studio 10.0\VC\vcvarsall.bat x86 set MSVCVER=9.0 set PATH=D:\XSLT\Xalan-C_1_10_0\bin;%PATH% %comspec% /k title Environment for ooRexx-main (%config%) -- Get a FREE DOWNLOAD! and learn more about uberSVN rich system, user administration capabilities and model configuration. Take the hassle out of deploying and managing Subversion and the tools developers use with it. http://p.sf.net/sfu/wandisco-d2d-2___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] rxapi abends ...
Dear Jean-Louis, On 20.08.2011 16:03, Jean-Louis Faucher wrote: You probably have already all what needed to build several versions of ooRexx. But just in case, I attached files which set environment for 4.1.0 and main (adjust to your own paths). This is a simplified version of the scripts I use, but they are enough to build/test. When you double-clic on one of them (after renaming .txt to .bat), a cmd shell is opened. Enter : cdtrunk makeorx DEBUG From here, you can test your scripts. thank you *very* much, indeed ! Best regards, ---rony -- Get a FREE DOWNLOAD! and learn more about uberSVN rich system, user administration capabilities and model configuration. Take the hassle out of deploying and managing Subversion and the tools developers use with it. http://p.sf.net/sfu/wandisco-d2d-2 ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
