search for: smnprintf

Displaying 4 results from an estimated 4 matches for "smnprintf".

Did you mean: scnprintf
2018 Aug 17
4
Call for testing: OpenSSH 7.8
...15:06, Val Baranov <val.baranov at duke.edu> wrote: [...] > test_utf8: ........................ > regress/unittests/utf8/tests.c:48 test #25 "c_esc" > ASSERT_INT_EQ(len, wantlen) failed: > len = -1 > wantlen = 5 This boils down to meaning OpenSSH's smnprintf call failed for the string "\033x" instead of returning the expected escaped version "\\033x". The code is in utf8.c but I am not sure why it failed. What's your locale set to? You can run the rest of the tests on your platform by running: TEST_SSH_UTF8=no make testst --...
2018 Aug 20
2
Call for testing: OpenSSH 7.8
...e.edu> wrote: >>> test_utf8: ........................ >>> regress/unittests/utf8/tests.c:48 test #25 "c_esc" >>> ASSERT_INT_EQ(len, wantlen) failed: >>> len = -1 >>> wantlen = 5 >> This boils down to meaning OpenSSH's smnprintf call failed for the >> string "\033x" instead of returning the expected escaped version >> "\\033x". The code is in utf8.c but I am not sure why it failed. > Actually, it is *supposed* to fail unless the locale is either > UTF-8 or the POSIX (ASCII) locale, be...
2018 Aug 18
2
Call for testing: OpenSSH 7.8
...wrote: > >>> test_utf8: ........................ >>> regress/unittests/utf8/tests.c:48 test #25 "c_esc" >>> ASSERT_INT_EQ(len, wantlen) failed: >>> len = -1 >>> wantlen = 5 > >> This boils down to meaning OpenSSH's smnprintf call failed for the >> string "\033x" instead of returning the expected escaped version >> "\\033x". The code is in utf8.c but I am not sure why it failed. > > Actually, it is *supposed* to fail unless the locale is either > UTF-8 or the POSIX (ASCII) loca...
2018 Aug 20
2
Call for testing: OpenSSH 7.8
........................... >>>>> regress/unittests/utf8/tests.c:48 test #25 "c_esc" >>>>> ASSERT_INT_EQ(len, wantlen) failed: >>>>> len = -1 >>>>> wantlen = 5 >>>> This boils down to meaning OpenSSH's smnprintf call failed for the >>>> string "\033x" instead of returning the expected escaped version >>>> "\\033x". The code is in utf8.c but I am not sure why it failed. >>> Actually, it is *supposed* to fail unless the locale is either >>> UTF-...