User forums > Help

Unable to read source file

<< < (8/8)

ked:
Hi there!
I encountered exactly the same problem with both installations of c::b 16.01 and 17.12, regardless of wx2.x/wx3.x on a Win 10 subsystem for Linux Ubuntu installation (Bionic ver). It seemed completely random which files c::b displayed or not. All files I've tested are completely equal in terms of encoding, permissions, etc. and fully visible in other editors (vi, emacs, gedit, etc) so the discovery of the file size < 617B issue by tianrenli92 really saved my day, and probably the coming week!!! Thank you!!!
The quick fix is of course just to add a few # signs in the files smaller than 617B, but a bug-fix is probably appreciated  ;)

What is the latest news about this issue? Could not find anything about it elsewhere...

oBFusCATed:

--- Quote from: ked on January 17, 2019, 07:37:52 am ---What is the latest news about this issue? Could not find anything about it elsewhere...

--- End quote ---
Same as before. Someone has to install a debugger, build debug versions of cb and wx and try to see what is going on.

I have enough platforms, so I cannot bother to debug another one. Sorry.

ked:
Thanx anyway for discovering the file size relation to the problem. I can live with adding #-es to exceed the critical file size, and debugging c::b source code (and similar) is, however, waaaay out of my knowledge.

BlueHazzard:
no windows 10 to debug :/

Miguel Gimenez:
I have Windows 10 (64 Pro and 32 Home) and don't have such problem with a 71 byte long file.

I think it is related to the Windows Subsystem for Linux file system adaption layer, both posters are using it.

Navigation

[0] Message Index

[*] Previous page