Re: Failed to set breakpoint

On 04/04/2014 03:44 PM, Alan Baljeu wrote:
> I expect it's the reloading with a different name that causes the problem.

Shouldn't be a problem as long as the compiled code is in sync with the 
source.  But, as often the case, there seems to be more involved than 
just loading this bit of code ...  That is why problem reports should be
self-contained and include version details, what to do to reproduce, 
what is expected and what happens and how the `happens' differs from
the `expected'.  Sometimes some of this is totally obvious, so you
can leave it out.  E.g., if `what happens' is a crash, you don't have to
explain how that differs from an expected A = 42.

	Cheers --- Jan

>
> Alan Baljeu
> ------------------------------------------------------------------------
> *From:* Jan Wielemaker <[email protected]>
> *To:* Alan Baljeu <[email protected]>; Prolog
> <[email protected]>
> *Sent:* Friday, April 4, 2014 4:34:15 AM
> *Subject:* Re: [SWIPL] Failed to set breakpoint
>
> On 04/03/2014 09:51 PM, Alan Baljeu wrote:
>
>  > I have a file loaded containing the following generated predicate
>  > among others. �Pcemacs refuses to set a breakpoint on any line
>  > contained in it. �Other predicates in the same file, no problem. �But
>  > all predicates looking like this, problem. �If it matters, loop29 is
>  > generated, and the next time the file gets generated it may be called
>  > loop34. �
>  >
>  > loop29((Object, Key), [RefVar|M39], [ActiveVarId|N39]) :-
>  > ( ( RefVar= (Ref=_),
>  >  � �wait_instance_active(Object, Ref, ActiveVarId)
>  >  �),
>  >  �true
>  > ), !,
>  > loop29((Object, Key), M39, N39).
>  >
>  > loop29(_, [], []).
>
>
> I recall you're running 6.4.x?  This works fine in 7.1.11.  Proof
> attached.  Might also work in 6.6.
>
>      Cheers --- Jan
>
>
>
>

_______________________________________________
SWI-Prolog mailing list
[email protected]
https://lists.iai.uni-bonn.de/mailman/listinfo.cgi/swi-prolog