atom feed18 messages in org.apache.tcl.rivet-dev[Bug 57501] abort_page does not stop ...
FromSent OnAttachments
bugz...@apache.orgApr 17, 2015 8:12 am 
bugz...@apache.orgApr 17, 2015 9:28 am 
bugz...@apache.orgApr 17, 2015 10:54 am 
bugz...@apache.orgApr 17, 2015 11:58 am 
bugz...@apache.orgApr 18, 2015 6:52 am 
bugz...@apache.orgApr 18, 2015 10:16 am 
bugz...@apache.orgApr 20, 2015 12:52 pm 
bugz...@apache.orgApr 21, 2015 6:48 am 
bugz...@apache.orgApr 21, 2015 11:50 pm 
bugz...@apache.orgApr 27, 2015 8:20 am 
bugz...@apache.orgApr 29, 2015 9:27 am 
bugz...@apache.orgApr 30, 2015 5:41 pm 
bugz...@apache.orgMay 4, 2015 7:27 am 
bugz...@apache.orgMay 4, 2015 9:42 am 
bugz...@apache.orgMay 4, 2015 10:12 am 
bugz...@apache.orgMay 6, 2015 7:09 am 
bugz...@apache.orgMay 10, 2015 1:16 pm 
bugz...@apache.orgMay 12, 2015 9:43 am 
Subject:[Bug 57501] abort_page does not stop page execution after a call to ::rivet::parse
From:bugz...@apache.org (bugz@apache.org)
Date:May 4, 2015 10:12:24 am
List:org.apache.tcl.rivet-dev

https://bz.apache.org/bugzilla/show_bug.cgi?id=57501

--- Comment #27 from Massimo Manghi <mxma@apache.org> --- The latest patch prevents spurious error logging by checking the flag globals->page_aborting (Tcl interpreter associated data) but there also cases when you want to print an error even when abort_page has been called

After abort_page is called execution is interrupted and control passed on to AbortScript and AfterEveryScript. If any of these scripts fail for some reason logging must be re-enabled and therefore that flag must be reset each time an error handler is called (Rivet_ExecuteErrorHandler)

This simple change is in my working box, I'm certain your AbortScript is fail proof ;) so it won't change your tests. I will check it more closely and commit it in a day or two