Alex
Alex
well, having some time and desire and ... was able to reproduce it... steps: just walking on assemblies references deep diving into lower levels,etc:  Maybe stack tracke will help...
the tools in this repo handles .pyc files you provided plain text .py module what is your question about then?
I believe the tools in this repo does not solve the readability issues, sorry you need to find some tool simlar like de4dot for .net world that is capable of...
yeah good point! then I suggest to put some note in last column....
better to attach sample .pyc that lead to issues...
it's already documented - https://github.com/zrax/pycdc#building-decompyle
Idea aloud - or maybe this is happening only on debug builds??
Nope, release build has same problem of sudden stop...
@siegfriedpammer could it be done in current implementation of ILSpy? or this is new feature req
I mean if say a binary has 10 classes and 100 functions overall and during saving a project (full decompilation) we hit at least 1 error -> all process stops...