On 03/16/2017 04:44 PM, Theo van den Heuvel wrote:
> Earlier I tried using rakudobrew, before I learnt that that was
> actually discouraged,
> despite comments in doc/perlintro.pdf. I think I made a full clean-up.
perl6intro.com, which is where the pdf is generated from, has been
updated to no lon
bon jour Dominique,
I installed manually as explained on the rakudo website.
Earlier I tried using rakudobrew, before I learnt that that was actually
discouraged,
despite comments in doc/perlintro.pdf. I think I made a full clean-up.
Incidentily, I have no trouble using ANSIColor. I just have
On Friday, 10 March 2017 21:47:13 CET Theo van den Heuvel wrote:
> Strangely I do get messages like the following
>
> + EVAL_1 (1 - 1)
>
> | CompUnit::DependencySpecification.new(short-name =>
>
> "Terminal::ANSIColor",...
>
> about some modules (even some I wrote myself),
> but the interestin
Thanks Timo,
sadly. The result is similar "Cannot add breakpoint to unknown file
...".
I had been trying to remove .precomp directories, but I seem to be
missing something somewhere.
Strangely I do get messages like the following
LOADING EVAL_1
+ EVAL_1 (1 - 1)
| CompUnit::DependencySpeci
Heyo,
the way the debugger works is by changing the compiler to generate code
that communicates with the debugger at every step.
That means that if you want a module to be debuggable, it has to be
compiled by the debugger's compiler, too.
There's apparently currently no way to just force a full
On Fri, Mar 10, 2017 at 1:41 PM, Theo van den Heuvel
wrote:
> Hi all,
>
> the debugger, Debugger::UI::CommandLine, does not step into modules I use.
> I must be doing something wrong. Any ideas?
>
Same here.
I can add that I couldn't find a way to add a breakpoint in a module:
bp add absolute-p
