diff options
author | Kaz Kylheku <kaz@kylheku.com> | 2020-01-08 00:49:00 +0000 |
---|---|---|
committer | Kaz Kylheku <kaz@kylheku.com> | 2020-01-08 00:49:00 +0000 |
commit | 12fd1d7637c2fe5a4a6361aeb0f23997880cf1e2 (patch) | |
tree | 4729e3c6e2756d30cb145ccea6ff91bec97c8a26 /cadr.c | |
parent | e9ddfed55490cc9f41f700fb98340fa6a9536aaa (diff) | |
download | txr-12fd1d7637c2fe5a4a6361aeb0f23997880cf1e2.tar.gz txr-12fd1d7637c2fe5a4a6361aeb0f23997880cf1e2.tar.bz2 txr-12fd1d7637c2fe5a4a6361aeb0f23997880cf1e2.zip |
tests: broken glob test cases crash under musl.
Among several issues, the main one is that these
test cases use the str-d FFI type for strings.
This type means that TXR will take ownership of the
memory; it creates the Lisp strings for the Lisp array,
and then assuming that it has owership of the C strings,
it will free them. On musl, this causes an instant crash,
probably because the strings might not be individually
coming from malloc. The only documented interface for
freing glob resources is globfree; programs cannot assume
that the strings can be freed.
* tests/017/glob-carray.expected: Updated.
* tests/017/glob-carray.tl (glob-t): Add missing flags member
of type int. Change the array element string type from str-d
to str.
* tests/017/glob-zarray.tl: Likewise, and also add a comment
to explain why we are not calling globfree in this test case.
Diffstat (limited to 'cadr.c')
0 files changed, 0 insertions, 0 deletions