Ticket Created
over 4 years ago

WERETECH-10930

mdd command line debug timeout loading prg app

Per the documentation for ConnectIQ 3.2, it should be possible to use mdd as a command line debugger

mdd --help
usage: mdd [-d <arg>] [-e <arg>] [-h] [-x <arg>]
-d,--device <arg>    Device to simulate
-e,--executable <arg>CIQ executable (PRG) to debug
-h,--help            Print help message
-x,--debug-xml <arg> CIQ debug.xml of the provided PRG

For me, mdd mostly times out while loading the prg file.

There is a set timeout command (below) but this does not appear to change the behavour from the mdd command line or the file command within a session

(mdd) help set timeout
Set timeout limit to wait for the CIQ virtual machine to respond to NUM seconds.
Usage: set timeout NUM.

----------------------------------------------------------------------------------

(mdd) help file
Set the target executable, debug.xml, and device to simulate.
Usage: file EXECUTABLE DEBUG_XML DEVICE_ID
EXECUTABLE is a Connect IQ executable to run.
DEBUG_XML is the debug.xml generated during app compilation.
DEVICE_ID is the device to simulate.

File paths can have spaces as long as the path is wrapped in quotes.

For example

(mdd) set timeout 5000

(mdd) show timeout
The timeout limit is 5000 second(s).

(mdd) file bin/myApp.prg bin/myApp.prg.debug.xml edge520plus

Loading app: path_to_app\bin\myApp.prg

Failed to launch the app: Timeout

timeout occurs after roughly one second

The same for the command line directly:

mdd -d edge520plus -e bin/myApp.prg -x bin/myApp.prg.debug.xml
Connect IQ Version 3.2.5. Type "help" for more information.

Loading app: path_to_app\bin\myApp.prg

Failed to launch the device: Timeout
(mdd) quit

There are no spaces in the filenanes and I've tried with forward slashes and backward slashes

gary_l
  • over 4 years ago in reply to gary_l

    Thanks for your response. I am seeing the same thing as you are experiencing every time now.  It's likely that it isn't actually timing out which is why changing the timeout time limit doesn't effect how long it takes to fail. I'll pass the info along to the development team. 

  • over 4 years ago

    Hi Richard, apologies I meant to reply but got distracted when I realised the mdd logging had not been implemented:

    (mdd) set logging true
The "set logging" command is not yet implemented.

    In answer to your question, I have been able to recreate the issue with the BackgroundTimer sample from the v3.2.5 SDK (connectiq-sdk-win-3.2.5-2021-02-12-6d31f4357). This is the only SDK that have installed at the moment.

    Build command:

    monkeyc.bat -d edge520plus -f monkey.jungle -o BackgroundTimer.prg -w -y developer_key

    mdd command:

    C:\temp\samples>mdd -d edge520plus -e BackgroundTimer.prg -x BackgroundTimer.prg.debug.xml
Connect IQ Version 3.2.5. Type "help" for more information.

Loading app: C:\temp\samples\BackgroundTimer.prg

Failed to launch the app: Timeout
(mdd) set timeout 5000

(mdd) show timeout
The timeout limit is 5000 second(s).

(mdd) file BackgroundTimer.prg BackgroundTimer.prg.debug.xml edge520plus
Killing app: C:\temp\samples\BackgroundTimer.prg

Loading app: C:\temp\samples\BackgroundTimer.prg

Failed to launch the app: Timeout

    I have uploaded the prg and debug.xml @ https://fromsmash.com/BackgroundTimerSample

    My application also uses a background process, so I wonder if that might be the cause?

  • over 4 years ago

    Gary, would you be able to provide a .prg file that you are encountering this issue with? So far we have been unable to reproduce the same issue you are experiencing. 

  • over 4 years ago

    Hi, we have made an internal ticket to look into this. Does this issue occur 100% of the time with every .prg file you've tried? I've personally tried several and haven't run into this yet which leads me to believe it is related to the .prg file specifically.