Strange behaviour around fs.statSync #430
Replies: 4 comments
-
Posted at 2015-06-17 by @gfwilliams Thanks - that looks interesting. I'll have a look and see if I can reproduce it. I can't see anything immediately wrong in |
Beta Was this translation helpful? Give feedback.
-
Posted at 2015-06-17 by JumJum Just tried to reproduce syncStat problem in a different way. Typed commands in terminal window:
|
Beta Was this translation helpful? Give feedback.
-
Posted at 2015-06-17 by @gfwilliams What's in I just tried this on an Espruino board with 1v79 from the website and it seems to work, so maybe my file Having said that, I found that if |
Beta Was this translation helpful? Give feedback.
-
Posted at 2015-06-17 by @gfwilliams Nope, now it's breaking! As you say, doing a
Looks like this is something else dodgy in the SPI/Filesystem interface code :( |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Posted at 2015-06-17 by JumJum
running this prints "..." on screen, so variable startAt is corrupted
uncommented first console.log and it works fine:
Also had problems sometimes by using fs.statSync from terminal window. Connection to com-port was lost, and I had to reset and restart everything.
IMHO, this could be a problem around memory management for fs.statSync.
Using 1v80 on Espruino Board
Data returned from readFile is this:
Beta Was this translation helpful? Give feedback.
All reactions