As, in general, a Prolog source file defines a single module, we can simply compile the Prolog files as Logtalk files. Re-run your program in debug mode (:- debug.) to get more detail. Prolog modules The Logtalk compiler supports compiling modules (that only make use of a common subset of directives) as objects. Note: some frames are missing due to last-call optimization. It adds 15 new linter checks, notably for possibly non-steadfast predicates, predicate and variable names that do not follow coding guidelines, repeat loops without a cut, redundant calls to built-in predicates and control constructs, cuts in clauses for multifile predicates, variable use in all-solutions predicate calls, and several others. This translates to a different, although similar, set of debugging features when compared with some of the more sophisticated Prolog debuggers. httpd_wrapper:handler_with_output_to(http_dispatch:time_limit_action(.),287391,-,current_output,error(goal_failed(.),context(_2130,_2132))) at /home/jan/lib/swipl/library/http/http_:308 First, unlike most Prolog debuggers, the Logtalk debugger is not a built-in feature but a regular Logtalk application using documented debugging hook predicates. catch(httpd_wrapper:call_handler(.,287391,-),error(goal_failed(.),context(_2056,_2058)),httpd_wrapper:true) at /home/jan/lib/swipl/boot/:562 Logtalk programmer: writing the application, have SWI Prolog and Logtalk installed Prolog programmer: writing only on one or two special source files in the. setup_call_catcher_cleanup(time:alarm(20.),time:run_alarm_goal(.),_1926,time:remove_alarm_notrace(.)) at /home/jan/lib/swipl/boot/:663 http_dispatch:call_action(pack:pack_file_details,) at /home/jan/lib/swipl/library/http/http_:1044 Goal unexpectedly failed: pack:pack_file_details()

500 Internal server error Internal server error

Logtalk prolog