Re: [Eclipse-clp-bugs] ECLiPSe Tracer bug

[Kish S. <kis...@gm...>]

Hi Mark,

Yes, I am still around. I don't know if Joachim answered your question, but
in case he hasn't..

If by 'not printing names', you mean the ... in CALL port for ..  = ...,
then as far as I remember, this was always the case for =/2 (and probably
some other built-ins), because of the way they are compiled.

You should see the source line for the call in the 'source context' tab,
and that should give you the names.

If you want to see the values for the call as well, you can add a dummy
goal before the =/2, e,g, writeln(X,Y), X = Y to see the values.

Kish


On Tue, Jul 28, 2020 at 5:02 PM Mark Wallace via Eclipse-clp-bugs <
ecl...@li...> wrote:

> Hi Joachim,
> Is Kish still active?
> The ECLiPSe tracer stopped printing out names.
> I just downloaded the latest public release of ECLiPSe 7.0 for Windows
> 64bit, and have the same bug:
> [image: image.png]
> It's frustrating - I can't find my bug which occurs in an infinite loop!
>     Cheers
>         Mark
> --
>
> *Mark Wallace  *
> Professor
> *Information Technology*
> My days of work are *Tuesdays, Wednesdays and Fridays*
> Monash University, Level 6, Building H, Caulfield Campus, 900 Dandenong
> Road, Caulfield East VIC 3145, Australia
> T: +61 (0)3 9903 4276                      M: +61 0400 868 629
>                   E: mar...@mo... <nam...@mo...>
>
> *We acknowledge and pay respect to the Traditional Owners and Elders -
> past, present and emerging - of the lands on which Monash University is
> located.*
> _______________________________________________
> Eclipse-clp-bugs mailing list
> Ecl...@li...
> https://lists.sourceforge.net/lists/listinfo/eclipse-clp-bugs
>