6 Replies Latest reply on Jan 16, 2013 3:18 PM by Alexander Babichev

    RhoConnect not starting when debugging

    Rutger van Eerd

      Hello,

       

      When I start my RhoConnect application from RhoStudio using "Run" my application starts and runs. When I try to start it using "Debug" RhoConnect does not start. Rredis however does start. Any ideas?

       

      I'm using RhoStudio 2.0.0.201211162257.

       

      Regards,

      Rutger

        • Re: RhoConnect not starting when debugging
          Peter Arcuri

          Can't say for sure if that is an issue with RhoStudio v2.0 but I've seen much inprovements over the last 2 releases. You may want to upgrade to version 2.2.1.12.

          • RhoConnect not starting when debugging
            Rutger van Eerd

            I am using RhoMobile Suite 2.2.1.12. Apparently this comes with RhoStudio 2.0.0.201211162257. Just as Rhodes and RhoConnect have different versions. So I am using the latest version. Any other ideas? Can I check some logfile to see whats going wrong/what is missing?

            • Re: RhoConnect not starting when debugging
              Rutger van Eerd

              This variable is already correctly set. Note that when running the application RhoConnect does start but when debugging it does not.

               

              When I run the application I see this in the build console:

               

              build started

               

              PWD: D:\RhoStudio\RhoconnectApplication1

              CMD: rhoconnect stop

              Kan bestand C:/TMP/rhoconnect.pid niet vinden.

              RET: 0

               

              PWD: D:\RhoStudio\RhoconnectApplication1

              CMD: rhoconnect redis-stop

              RET: 0

               

              PWD: D:\RhoStudio\RhoconnectApplication1

              CMD: rhoconnect redis-startbg

              Starting redis in a new window...

              RET: 0

               

              PWD: D:\RhoStudio\RhoconnectApplication1

              CMD: start cmd /c rhoconnect start&&exit

              RET: 0

               

              When I debug the application I see this:

               

              build started

               

              PWD: D:\RhoStudio\RhoconnectApplication1

              CMD: rhoconnect stop

               

              D:\RhoStudio\RhoconnectApplication1>taskkill /F /PID 3804

              Het proces met pid 3804 is be‰indigd.

              RET: 0

               

              PWD: D:\RhoStudio\RhoconnectApplication1

              CMD: rhoconnect redis-stop

              RET: 0

               

              PWD: D:\RhoStudio\RhoconnectApplication1

              CMD: rhoconnect redis-startbg

              Starting redis in a new window...

              RET: 0

               

              So the command to run my application is not executed. Any idea why? Do run and debug use different build scripts? Probably the debug build script is missing the command to run RhoConnect.

              • Re: RhoConnect not starting when debugging

                I use RhoStudio   2.0.0.201211162257 and I'm able to start rhoconnect app under debugger:

                 

                PWD: C:\workspace\ProductServer

                CMD: rhoconnect stop

                 

                C:\workspace\ProductServer>taskkill /F /PID 1232

                ERROR: The process "1232" not found.

                RET: 0

                 

                PWD: C:\workspace\ProductServer

                CMD: rhoconnect redis-stop

                RET: 0

                 

                PWD: C:\workspace\ProductServer

                CMD: rhoconnect redis-startbg

                Starting redis in a new window...

                RET: 0

                ...

                So you should be able to start app in debugger. 

                 

                But, unfortunately, debugger is broken in latest release due to ruby bug #7180: https://bugs.ruby-lang.org/issues/7180#change-32571

                In result, on 1st call  to redis API debugger freezes.

                We found workaround to work properly ruby function set_trace_func (it used by debugger) , but it was too late (moto release cycle is so long!) and fix has not been included in release. Wait for next release, pls.