@anybody ever finding this through google: In the end the only way I succeeded doing this was by placing a cfthrow tag inside a cftry/catch, catching the error itself and examining the callstack as seen in the cfthrow. David
On Thursday, March 7, 2013 10:46:15 AM UTC+1, David Mulder wrote: > > Hi guys, > Any idea how I could retrieve the call stack? In adobe CF you have > callStackGet() > and callStackDump(), but both are't supported in openbd. Maybe some quick > java hack or something? Oh well, doubt it, but it would have been useful to > show which line of code triggered an error page to show without it needing > to pass this information explicitly. > Greetings, > David > -- -- online documentation: http://openbd.org/manual/ http://groups.google.com/group/openbd?hl=en --- You received this message because you are subscribed to the Google Groups "Open BlueDragon" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
