In Applescript, how to get a line number or stack trace on error

applescripterror

I'm writing some fairly complex Applescripts, but when something goes wrong – Apple event timed out – or similar, I can't tell precisely where it failed.

At the moment, I'm wrapping all handlers with try blocks, with an on error that re-raises the error, with a reference to the handler name and the value of a variable that I set at various points through the handler so I can isolate the error to somewhere between two points.

** Is there a way to get Applescript to say 'Apple event timed out at line 15 in await(), at line 60 in connectRemoteUser(), at line 90 in autostartTestUsers()' without having to code it all directly?

I can't rely on the script editor's location highlighting because the errors happen intermittently when the script is out in production.

Best Answer

It's ugly but it works...

try
    set marker to 1
    -- do stuff
    set marker to 2
    -- do stuff
    set marker to 3
    1 / 0
    set marker to 4
on error errMsg number errNum
    tell application "SystemUIServer"
        display alert (marker & space & errMsg & return & return & "Error number " & errNum as text) buttons "Cancel" cancel button "Cancel"
    end tell
end try

Related Solutions

Error in applescript “Invalid index”

The values you set before are not given via the inputparameter. As long as you run your Automator Workflow as an Automator Workflow and not as an Application or Service, you can access your formerly set variables using the following:

tell application "Automator"
    set cat to value of variable "NameOfFirstVariable" of front workflow
    set x to value of variable "NameOfSecondVariable" of front workflow
    set o to value of variable "NameOfThirdVariable" of front workflow
end tell

inside your "Run Applescript" action.

Greetings, Michael / Hamburg

MacOS – Simple 3 line applescript – Error -128

Your headache lays with how Steam handles its exit status. Steam probably doesn't have applescript integration, so it considers a quit command from applescript an unclean exit. It would still quit, but it will let you know about it. What you need is a way to ignore the error message and execute the rest of the script nevertheless.

try
    tell application "Steam" to quit
    on error error_message number error_number
        if error_number is equal to -128 then
        --Keep Calm and Carry On
        else
            display dialog error_message
        end if
end try
delay 5
tell application "Plex Home Theater" to activate

You can combine the two scripts into one toggle/switch:

set steamRunning to false
set plexRunning to false

try
    do shell script "pgrep -l -f 'Steam.app'"
    set steamRunning to true
end try

try
    do shell script "pgrep -l -f 'Plex Home Theater'"
    set plexRunning to true
end try

if steamRunning is true and plexRunning is false then

    try
        tell application "Steam" to quit
    on error error_message number error_number
        if error_number is equal to 128 then
            --Keep Calm and Carry On
        else
            display dialog error_message
        end if
    end try
    delay 5
    tell application "Plex Home Theater" to activate

end if


if steamRunning is false and plexRunning is true then

    tell application "Plex Home Theater" to quit
    delay 5
    tell application "Steam" to activate

end if

I don't have either app so I cannot debug. There could be multiple processes named "steam", given its game-thing, so I used "Steam.app", assuming that's the app name under /Applications/.

Best Answer

Related Solutions

Error in applescript “Invalid index”

MacOS – Simple 3 line applescript – Error -128

Related Question