← Back to team overview

sikuli-driver team mailing list archive

[Bug 1234831] Re: IDE 1.0.1 hangs launching "-d 3 -c" on OS X

 

Yep, it does not make sense, to be able to add -c into the IDE's startup
dialog, since you do not have a stdout like when running in a terminal
session.

Using option -d in this case will redirect all output produced by the
logging feature to a file as said. Normal user generated output (e.g.
print will still go to the message area.

If you want to have a full log from beginning (including IDE startup and
all user generated output), you have to run the IDE from command line
with these parameters.

** Changed in: sikuli
       Status: New => Fix Committed

** Changed in: sikuli
   Importance: Undecided => High

** Changed in: sikuli
     Assignee: (unassigned) => RaiMan (raimund-hocke)

** Changed in: sikuli
    Milestone: None => 1.1.0

** Summary changed:

- IDE 1.0.1 hangs launching "-d 3 -c" on OS X
+ [1.0.1] IDE hangs using "-d 3 -c" in the startup dialog --- do not use -c

-- 
You received this bug notification because you are a member of Sikuli
Drivers, which is subscribed to Sikuli.
https://bugs.launchpad.net/bugs/1234831

Title:
  [1.0.1] IDE hangs using "-d 3 -c" in the startup dialog --- do not use
  -c

Status in Sikuli:
  Fix Committed

Bug description:
  Summary:  I launch Sikuli IDE 1.0.1 (build 12SEP2013160242) and enter
  "-d 3 -c" into the options dialog box that appears when launching the
  IDE and hit enter. The yellow message box appears but does not
  progress to a usable session.

  Environment: OS X 10.6.8 on a MacBook running Sikuli IDE 1.0.1
  Steps:
  1. Launch IDE.
  2. Enter "-d 3 -c" into the dialog box that appears on launching the IDE and hit enter.

  
  Expected: full log-in to IDE
  Actual:  IDE launch hangs at yellow dialog box. Must kill Sikuli process (using Activity Monitor or other means).

  Note: this is related to Related to Question #236745 in which entering "-d 3 -c" was recommended as a debugging measure.
  I will attach the crash log...

To manage notifications about this bug go to:
https://bugs.launchpad.net/sikuli/+bug/1234831/+subscriptions


References