[FLEX-18018] FDB 'run' fails with StringIndexOutOfBoundsException on Windows, if command processor produces AutoRun output

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Adobe Flex SDK 3.3 (Release)
• Fix Version/s: Adobe Flex SDK 4.0 (Release)
• Component/s: FDB - Debugger
• Environment: Affected OS(s): Windows; Language Found: English
• Assignee: Adobe JIRA
• Reporter: Adobe JIRA
• Created: 10/Mar/09 09:56
• Updated: 15/Apr/11 15:19
• Resolved: 23/Mar/09 15:02

Description

Steps to reproduce:
1. Edit registry key [HKCU\Software\Microsoft\Command Processor] - set value of "AutoRun" parameter to some command, that produces console output (e.g. "chcp 1251"). If "AutoRun" is missing, add it with type REG_SZ.
2. Start fdb
3. Try to debug any swf or html with 'run <filename>' command.

Actual Results:
Unexpected error while processing command.
For diagnostic purposes stack trace follows:
java.lang.StringIndexOutOfBoundsException: String index out of range: 30
at java.lang.String.substring(String.java:1935)
at flash.tools.debugger.DefaultDebuggerCallbacks.determineExeForType(DefaultDebuggerCallbacks.java:175)
at flash.tools.debugger.DefaultDebuggerCallbacks.recomputeExeLocations(DefaultDebuggerCallbacks.java:82)
at flash.tools.debugger.DefaultDebuggerCallbacks.getPlayerExe(DefaultDebuggerCallbacks.java:69)
at flash.tools.debugger.concrete.PlayerSessionManager$LaunchInfo.isPlayerNativeLaunch(PlayerSessionManager.java:170)
at flash.tools.debugger.concrete.PlayerSessionManager.launch(PlayerSessionManager.java:181)
at flex.tools.debugger.cli.DebugCLI.doRun(DebugCLI.java:4596)
at flex.tools.debugger.cli.DebugCLI.processLine(DebugCLI.java:6339)
at flex.tools.debugger.cli.DebugCLI.process(DebugCLI.java:723)
at flex.tools.debugger.cli.DebugCLI.execute(DebugCLI.java:565)
at flex.tools.debugger.cli.DebugCLI.main(DebugCLI.java:370)

Expected Results:
Flash Player or browser starts.

Workaround (if any):
Do not use AutoRun feature of Windows command processor