dd05be5d78
Original rationale behind using write in testutil was to accommodate no-stdio builds. But is there evidence that no-stdio users would have write or pre-defined meaning for file descriptors 1 and 2? Correct answer is to provide way for no-stdio users who want to exercise tests to plug in own BIO, not to make assumption that they have write. And since we don't have to make such assumption, we can as well go for simplest that works with standard library as specified by C language standard. Reviewed-by: Richard Levitte <levitte@openssl.org>
61 lines
1.2 KiB
C
61 lines
1.2 KiB
C
/*
|
|
* Copyright 2017 The OpenSSL Project Authors. All Rights Reserved.
|
|
*
|
|
* Licensed under the OpenSSL license (the "License"). You may not use
|
|
* this file except in compliance with the License. You can obtain a copy
|
|
* in the file LICENSE in the source distribution or at
|
|
* https://www.openssl.org/source/license.html
|
|
*/
|
|
|
|
#include "../testutil.h"
|
|
|
|
#include <openssl/crypto.h>
|
|
#include <openssl/bio.h>
|
|
|
|
BIO *bio_out = NULL;
|
|
BIO *bio_err = NULL;
|
|
|
|
void test_open_streams(void)
|
|
{
|
|
bio_out = BIO_new_fp(stdout, BIO_NOCLOSE | BIO_FP_TEXT);
|
|
bio_err = BIO_new_fp(stderr, BIO_NOCLOSE | BIO_FP_TEXT);
|
|
|
|
OPENSSL_assert(bio_out != NULL);
|
|
OPENSSL_assert(bio_err != NULL);
|
|
}
|
|
|
|
void test_close_streams(void)
|
|
{
|
|
BIO_free(bio_out);
|
|
BIO_free(bio_err);
|
|
}
|
|
|
|
int test_puts_stdout(const char *str)
|
|
{
|
|
return BIO_puts(bio_out, str);
|
|
}
|
|
|
|
int test_puts_stderr(const char *str)
|
|
{
|
|
return BIO_puts(bio_err, str);
|
|
}
|
|
|
|
int test_vprintf_stdout(const char *fmt, va_list ap)
|
|
{
|
|
return BIO_vprintf(bio_out, fmt, ap);
|
|
}
|
|
|
|
int test_vprintf_stderr(const char *fmt, va_list ap)
|
|
{
|
|
return BIO_vprintf(bio_err, fmt, ap);
|
|
}
|
|
|
|
int test_flush_stdout(void)
|
|
{
|
|
return BIO_flush(bio_out);
|
|
}
|
|
|
|
int test_flush_stderr(void)
|
|
{
|
|
return BIO_flush(bio_err);
|
|
}
|