33 replies to this topic

[littlesat]

Just a suggestion what you can do to continue debugging for the time being...

 

test = {"A": 1, "B": 2 }
for k, v in test.iteritems():
    print k, v

[Huevos]

 

Just a suggestion what you can do to continue debugging for the time being...

test = {"A": 1, "B": 2 }
for k, v in test.iteritems():
    print k, v

Yes in that instance. But you can't even output a "dir(obj)" for some methods. Like I say debuging or writing code is impossible now.

[littlesat]

Yes in that instance. But you can't even output a "dir(obj)" for some methods. Like I say debuging or writing code is impossible now.

 

I agree you want to do print dict and some debuggings might be less usefull... But you must also agree for long dicts/objects are also helpfull at all.... And you must also understand this is work in progression.... So later it is most likely fixed...

 

For now when you need own debugging you should implement a work-a-round...

Edited by littlesat, 26 February 2016 - 11:36.

[Taapat]

@Huevos maybe I miss something, but if you use your enigma build, where is the problem set buf size as large as you need?

[littlesat]

Too large is also no good... .... It is not a real solution... e.g. when you set it at 2048 we can again have lines of >2048 characters... ...

 

A dynamic solution should be solved without limits it time processing...

Edited by littlesat, 26 February 2016 - 19:25.

[Huevos]

@Huevos maybe I miss something, but if you use your enigma build, where is the problem set buf size as large as you need?

Having a big buffer is not the answer. The previous code used a 1024 buffer without this problem.

[betacentauri]

For Python output it used a string and not a 1024 byte char buffer (as far as I saw in the code).

[mirakels]

Actually, for python output there were no timestamps so were printed directly to screen. It no goes through the eDebug layer that uses buffers because it has been said strings are expensive (and I guess vsnprint() works on buffers and not on strings as destination)

[mirakels]

But then again I never actually saw the issue and also cannot find the example that Huevos is giving in the openpli engima code.

 

 

I may have a solution but have no example to test it on.

[Huevos]

But then again I never actually saw the issue and also cannot find the example that Huevos is giving in the openpli engima code.

 

 

I may have a solution but have no example to test it on.

If you have a fix I can test it. Just post the CPP file and I'll post the result.

Edited by Huevos, 26 February 2016 - 21:41.

[littlesat]

Just put print "*" * 2000 or so somewhere in the python code and you have the anomaly....

[mirakels]

ok, did an implementation.

[littlesat]

[Huevos]

Thanks for the fixes. Tested and working fine now.