I’m trying to debug and understand a (in my opinion) weird solution returned by gecode… I followed my request through the code of the ruby client (knife) through the code of the erlang API (chef_wm) through the code of the ruby depselector.rb. Until that
point I could reasonably following everything and all (temporarily added debug info) looked more or less logical and expected. But now I’m at the last stop, being the gecode lib itself. And debugging that one (in order to fully understand how it works) seems a little more challenging. Did some stuff in C++ before, but not too munch and quite a while ago ;) So when I noticed all
the debugging info in there, I tried it get it to spit out the logs but without any success. So anyone who can help me turn that on? Thx! |
Archive powered by MHonArc 2.6.16.