Hi Omar,
we’ve re-added the stack trace to the latest 11.0 snapshot [1], and will document this properly soon. I’ve slightly changed the behavior: Instead of a single descriptive string, the stack trace is now returned as a string sequence (the first entry points to the position in the code that failed, the following entries point to the function calls).
I would like to see $err:stack-trace added to the standard. I’ll give you an update if the QT4 group confirms that this is a good idea (might take a while).
Best, Christian
[1] https://files.basex.org/releases/latest/
On Thu, Jan 11, 2024 at 12:15 PM Omar Siam Omar.Siam@oeaw.ac.at wrote:
Hi,
Until 10.6 one could find the stack trace of an error in $err:additional. This feature is now gone from BaseX and the documentation.
I made my life much easier with reporting stack traces on errors in RestXQ endpoints. Now I don't see how to get that information anymore.
Any advice how to get this functionality back?
Best regards
-- Mag. Ing. Omar Siam Austrian Center for Digital Humanities and Cultural Heritage Österreichische Akademie der Wissenschaften | Austrian Academy of Sciences Stellvertretende Behindertenvertrauensperson | Deputy representative for disabled persons Bäckerstraße 13, 1010 Wien, Österreich | Vienna, Austria T: +43 1 51581-7295 omar.siam@oeaw.ac.at | www.oeaw.ac.at/acdh