On Sat, 7 Aug 2021 at 09:52, Neven Sajko <[email protected]> wrote: > I got an idea to debug this problem by replacing each occurence of the > `error "Invalid argument"` statement in those two files with a > statement that would cause a stack trace to be printed. That would > help further narrow down the issue. > > However, I don't even know if Fricas has the ability to issue stack > traces (from Spad code)?
I found out a bit more. This page has very useful info on debugging: http://fricas-wiki.math.uni.wroc.pl/DebuggingFriCAS Guided by that page, I did )set break break and then `backtrace` after running the offending integration. This seems to be the relevant call chain: error < valueOrPole < specialTrigs < itan < evaluate < elt < k2Elem0 < map Here valueOrPole, specialTrigs and itan, at least, are from elemntry.spad. However, specialTrigs calls valueOrPole in multiple places, so now I have to figure out on which line does the call happen. Neven -- You received this message because you are subscribed to the Google Groups "FriCAS - computer algebra system" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/fricas-devel/CAL%2BbK4PF1E_1SHeNy-AjAXu7F3cF1-dQ2ot_vFH-bdtF1%3DDX%2BA%40mail.gmail.com.
