It seems to be failing down in the bowels of the script engine (QSE.dll).
Can you add ScriptDebug=1 to your Toad.ini file and try that script again? It will create two files in your userfiles dir - ToadScriptDebug.txt and qsetrace.log. Please send those along...they provide some very detailed logging of what is going on in the script engine.
Thanks,
Greg
From: Michael Staszewski [mailto:bounce-mstaszew@toadworld.com]
Sent: Tuesday, September 08, 2015 9:34 AM
To: toadoraclebeta@toadworld.com
Subject: RE: [Toad for Oracle - Beta Discussion Forum] Toad 12.8 crashed on read from address EF
RE: Toad 12.8 crashed on read from address EF
Reply by Michael Staszewski
Interestingly enough the error you had from 9/4 is in there as well and for the same issue as your current one.
Extending the file instead of overwriting is by design. At one time it would maintain the previous 32 exception and then during an upgrade a few releases ago it was accidentally changed to maintain the last 1 exception. It again maintains the last 32 which is good for cascading exception scenarios where the first is the real problem, but subsequent exceptions were blowing away the initial one in the log.
Michael
On 09/08/2015 09:14 AM, kornelis.abe wrote:
RE: Toad 12.8 crashed on read from address EF
Reply by kornelis.abe
Gregory,
The logger has extended the file in stead of overwriting it.
Check the log and find that it contains 4 errorlogs.
The latest one is the one related to this issue.
Kind regards,
Abe
===
To reply, please reply-all to this email.
Stop receiving emails on this subject.
Or
Unsubscribe from Toad for Oracle - Beta notifications altogether.
Toad for Oracle - Beta Discussion Forum
Flag
this post as spam/abuse.
To reply, please reply-all to this email.
Stop receiving emails on this subject.
Or
Unsubscribe from Toad for Oracle - Beta notifications altogether.
Toad for Oracle - Beta Discussion Forum
Flag
this post as spam/abuse.