blob: d539f0bad44cf3aeba4a53c39986b990f8914776 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
|
/* BZ #24024 strerror and errno test.
Copyright (C) 2019 Free Software Foundation, Inc.
This file is part of the GNU C Library.
The GNU C Library is free software; you can redistribute it and/or
modify it under the terms of the GNU Lesser General Public
License as published by the Free Software Foundation; either
version 2.1 of the License, or (at your option) any later version.
The GNU C Library is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
Lesser General Public License for more details.
You should have received a copy of the GNU Lesser General Public
License along with the GNU C Library; if not, see
<https://www.gnu.org/licenses/>. */
#include <dlfcn.h>
#include <errno.h>
#include <string.h>
#include <support/check.h>
#include <support/support.h>
/* malloc is allowed to change errno to a value different than 0, even when
there is no actual error. This happens for example when the memory
allocation through sbrk fails. Simulate this by interposing our own
malloc implementation which sets errno to ENOMEM and calls the original
malloc. */
void
*malloc (size_t size)
{
static void *(*real_malloc) (size_t size);
if (!real_malloc)
real_malloc = dlsym (RTLD_NEXT, "malloc");
errno = ENOMEM;
return (*real_malloc) (size);
}
/* strerror must not change the value of errno. Unfortunately due to GCC bug
#88576, this happens when -fmath-errno is used. This simple test checks
that it doesn't happen. */
static int
do_test (void)
{
char *msg;
errno = 0;
msg = strerror (-3);
(void) msg;
TEST_COMPARE (errno, 0);
return 0;
}
#include <support/test-driver.c>
|
