Use binary mode when opening via fopen in the tools (#2371)

In the snapshot tool the files were opened
in text mode. However the snapshot files
are binary files thus it is advised to use the
binary mode when opening the files.

Specifying the binary mode is a must on Windows
platform otherwise the read/write operations
are inserting extra '\r' characters.

To make the tools consitent across OSes all
fopen are now opening files in binary mode.

Also update jerry-libc to accept the 'b'
modifier and add a test case where the JS
file uses CR-LF line endings.

JerryScript-DCO-1.0-Signed-off-by: Peter Gal [email protected]
This commit is contained in:
Péter Gál authored and yichoi committed 2018-06-12 04:38:35 +09:00
1 parent 9ae60a4910
commit efa8850783
5 files changed
+41 -10

No files matched your search

+13 -4
View File
@@ -113,16 +113,25 @@ fopen (const char *path, /**< file path */
bool truncate = false;
bool create_if_not_exist = false;
bool position_at_end = false;
int modifier_position = 1;
assert (path != NULL && mode != NULL);
assert (mode[1] == '+' || mode[1] == '\0');
assert (mode[1] == '\0'
|| (mode[1] == '+' && mode[2] == '\0')
|| (mode[1] == 'b' && mode[2] == '\0')
|| (mode[1] == 'b' && mode[2] == '+' && mode[3] == '\0'));
if (mode[1] == 'b')
{
modifier_position = 2;
}
switch (mode[0])
{
case 'r':
{
may_read = true;
may_write = (mode[1] == '+');
may_write = (mode[modifier_position] == '+');
break;
}
case 'w':
@@ -130,7 +139,7 @@ fopen (const char *path, /**< file path */
may_write = true;
truncate = true;
create_if_not_exist = true;
may_read = (mode[1] == '+');
may_read = (mode[modifier_position] == '+');
break;
}
case 'a':
@@ -138,7 +147,7 @@ fopen (const char *path, /**< file path */
may_write = true;
position_at_end = true;
create_if_not_exist = true;
if (mode[1] == '+')
if (mode[modifier_position] == '+')
{
assert (false && "unsupported mode a+");
}