You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue is fixed by #926, issue report opened for tracking. The haystack/big and needle/small arguments to strstr must be null-terminated C strings, but archive_write_ar_header calls strstr with a not-terminated character sequence.
Version of libarchive: 3.3.2 in FreeBSD How you obtained it: included as part of FreeBSD Operating system and version: FreeBSD + clang500-import branch, as of June 2017 What compiler and/or IDE you are using: Clang 5.0.0 snapshot July 5 2017
Description of the problem you are seeing: What did you do? Use FreeBSD ar (libarchive consumer) to create an archive (static library), as part of the Virtualbox port build What did you expect to happen? Static library is created successfully What actually happened? ar segfaults What log files or error messages were produced?
From report at https://lists.freebsd.org/pipermail/freebsd-emulation/2017-July/015299.html
How the libarchive developers can reproduce your problem: What other software was involved? FreeBSD ar What other files were involved? Virtualbox 5.1.22 How can we obtain any of the above?
The text was updated successfully, but these errors were encountered:
This issue is fixed by #926, issue report opened for tracking. The haystack/big and needle/small arguments to strstr must be null-terminated C strings, but
archive_write_ar_headercalls strstr with a not-terminated character sequence.Version of libarchive: 3.3.2 in FreeBSD
How you obtained it: included as part of FreeBSD
Operating system and version: FreeBSD + clang500-import branch, as of June 2017
What compiler and/or IDE you are using: Clang 5.0.0 snapshot July 5 2017
Description of the problem you are seeing:
What did you do? Use FreeBSD ar (libarchive consumer) to create an archive (static library), as part of the Virtualbox port build
What did you expect to happen? Static library is created successfully
What actually happened? ar segfaults
What log files or error messages were produced?
From report at https://lists.freebsd.org/pipermail/freebsd-emulation/2017-July/015299.html
Backtrace at fault:
Another report at https://lists.freebsd.org/pipermail/freebsd-current/2017-July/066567.html
How the libarchive developers can reproduce your problem:
What other software was involved? FreeBSD ar
What other files were involved? Virtualbox 5.1.22
How can we obtain any of the above?
The text was updated successfully, but these errors were encountered: