I'm curious to know why you'd need/want this? Stacktraces in CFML runtime errors would be of little or no use to a CFML developer, and only limited use to the engine developers (BD Internal Server errors, on the other hand, do include stacktraces that are useful to engine developers).
Vince On Mar 17, 9:38 am, Randy Merrill <[email protected]> wrote: > I guess examples will help a lot ;) > > I've attached screenshots of the big three engines. > > With a simple test page: > > <cftry> > <cfthrow message="Testing" /> > <cfcatch> > <cfdump var="#cfcatch#" /> > </cfcatch> > </cftry> > > You'll notice that CF9 and Railo both have a string version of stacktrace > available at cfcatch.stacktrace but OpenBD does not. > > This was tested on a nightly openBD from yesterday. > -- > Randy Merrill > > cf9Catch.png > 118KViewDownload > > OpenBDCatch.png > 50KViewDownload > > RailoCatch.png > 139KViewDownload -- Open BlueDragon Public Mailing List http://www.openbluedragon.org/ http://twitter.com/OpenBlueDragon mailing list - http://groups.google.com/group/openbd?hl=en !! save a network - please trim replies before posting !!
