Hi Anton,
I assume that the main issue you're interested in is in being able to debug applications that use both Logtalk/Prolog and Java code? Do you want to as seamlessly possible transitioning from one debugger to the other when there's an inter-language call?
Can you confirm/clarify?
Cheers,
Paulo
>> an email to swi-prolog+unsubscribe@googlegroups.com
>> <mailto:swi-prolog+unsub...@googlegroups.com>.
>> Visit this group at https://groups.google.com/group/swi-prolog.
>> For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to the Google Groups "SWI-Prolog" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to swi-prolog+unsubscribe@googlegroups.com.
> Visit this group at https://groups.google.com/group/swi-prolog.
> For more options, visit https://groups.google.com/d/optout.
-----------------------------------------------------------------
Paulo Moura
Logtalk developer
Email: <mailto:pmo...@logtalk.org>
Web: <http://logtalk.org/>
-----------------------------------------------------------------
--
You received this message because you are subscribed to the Google Groups "SWI-Prolog" group.
To unsubscribe from this group and stop receiving emails from it, send an email to swi-prolog+unsubscribe@googlegroups.com.
Hi,
I'm sorry for delayed post.
I'm trying to write the sketched description of inter-language debugger.
I'd like to clarify some aspects to make sure that we're talking about
the same things.
1. Java application is debugged using JDI i.e. 2 processes for 2 JVMs.
1st JVM debugger (process#1) controls debugging (using GUI)),
2nd (remote) JVM - debuggee(process#2) (that executes the application).
2. Logtalk is compiled to backed Prolog in debug mode.
So we deal with Prolog interpreter executing code with the
clauses wrapped by Logtalk;
Debugger should map this clauses to Logtalk (GUI)
Further, as in Prolog.
3. Prolog uses its own debugger.
4. Inter-language calls.
Correct me if I'm wrong - in debug mode we, in principle, could
switch Logtalk from current backed Prolog to the one
implemented in Java (JIProlog, GNU Prolog for Java, tuProlog).
So, we will have two similar debug units from item 1:
First for java debugging ( process#1,2 )
Second for Java-Prolog ( process#3,4 )
Also, maybe there's the reason to have a look at PDT or something like this,
>> >> an email to swi-prolog+unsubscribe@googlegroups.com
>> >> <mailto:swi-prolog+unsub...@googlegroups.com>.
>> >> Visit this group at https://groups.google.com/group/swi-prolog.
>> >> For more options, visit https://groups.google.com/d/optout.
>> >
>> > --
>> > You received this message because you are subscribed to the Google Groups "SWI-Prolog" group.
>> > To unsubscribe from this group and stop receiving emails from it, send an email to swi-prolog+unsubscribe@googlegroups.com.
>> > Visit this group at https://groups.google.com/group/swi-prolog.
>> > For more options, visit https://groups.google.com/d/optout.
>>
>> -----------------------------------------------------------------
>> Paulo Moura
>> Logtalk developer
>>
>> Email: <mailto:pmo...@logtalk.org>
>> Web: <http://logtalk.org/>
>> -----------------------------------------------------------------
>>
>>
>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups "SWI-Prolog" group.
>> To unsubscribe from this group and stop receiving emails from it, send an email to swi-prolog+unsubscribe@googlegroups.com.
>> Visit this group at https://groups.google.com/group/swi-prolog.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> -----------------------------------------------------------------
> Paulo Moura
> Logtalk developer
>
> Email: <mailto:pmo...@logtalk.org>
> Web: <http://logtalk.org/>
> -----------------------------------------------------------------
>
>
>
>
> --
> You received this message because you are subscribed to a topic in the Google Groups "SWI-Prolog" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/topic/swi-prolog/_7CZlBngwIo/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to swi-prolog+unsubscribe@googlegroups.com.
IntelliJ should provide a convenient abstraction layer for this. Maybe ask a pointer in the IntelliJ forum ?
Paulo, would you say that a useful debugging tool would be something that will allow us to visualize the full explanation of a proof, while stopping and inspecting on breakpoints defined somehow in clauses ?
Anton, I would definitely take a look to how debugging and/or visualization of proofs is currently done in SWI.
4. Inter-language calls.
Correct me if I'm wrong - in debug mode we, in principle, could
switch Logtalk from current backed Prolog to the one
implemented in Java (JIProlog, GNU Prolog for Java, tuProlog).
So, we will have two similar debug units from item 1:
First for java debugging ( process#1,2 )
Second for Java-Prolog ( process#3,4 )
Maybe, but I still think it may be a good idea to start it simple and try to get first a Logtalk debugger in the IntelliJ plugin. Then we could try to expand it to include Java interactions. Or do you think we should tackle the problem from the very beginning as a Prolog/Java debugger ?
>> >> <mailto:swi-prolog+unsubscribe@googlegroups.com>.