blob: af5e16e0f6e5b99be9f612cd055ff31e0ff43c9e (
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
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
|
other: 0.410
performance: 0.407
graphic: 0.361
device: 0.340
debug: 0.332
permissions: 0.325
semantic: 0.318
PID: 0.281
vnc: 0.269
network: 0.246
socket: 0.240
boot: 0.227
files: 0.219
KVM: 0.096
gccgo setcontext conftest crashes qemu-sh4
While testing gccgo on sh4 to add SH platform definitions to libgo, I discovered that the following conftest program which is part of the libgo configure script crashes on qemu-sh4:
(sid-sh4-sbuild)root@z6:/# cat setcontext.c
#include <pthread.h>
#include <stdlib.h>
#include <ucontext.h>
#include <unistd.h>
__thread int tls;
static char stack[10 * 1024 * 1024];
static ucontext_t c;
/* Called via makecontext/setcontext. */
static void
cfn (void)
{
exit (tls);
}
/* Called via pthread_create. */
static void *
tfn (void *dummy)
{
/* The thread should still see this value after calling
setcontext. */
tls = 0;
setcontext (&c);
/* The call to setcontext should not return. */
abort ();
}
int
main ()
{
pthread_t tid;
/* The thread should not see this value. */
tls = 1;
if (getcontext (&c) < 0)
abort ();
c.uc_stack.ss_sp = stack;
#ifdef MAKECONTEXT_STACK_TOP
c.uc_stack.ss_sp += sizeof stack;
#endif
c.uc_stack.ss_flags = 0;
c.uc_stack.ss_size = sizeof stack;
c.uc_link = NULL;
makecontext (&c, cfn, 0);
if (pthread_create (&tid, NULL, tfn, NULL) != 0)
abort ();
if (pthread_join (tid, NULL) != 0)
abort ();
/* The thread should have called exit. */
abort ();
}
(sid-sh4-sbuild)root@z6:/# gcc -o setcontext -lpthread setcontext.c
(sid-sh4-sbuild)root@z6:/# ./setcontext
Unhandled trap: 0x180
pc=0x7f69235e sr=0x00000000 pr=0x00400710 fpscr=0x00080000
spc=0x00000000 ssr=0x00000000 gbr=0x7f658478 vbr=0x00000000
sgr=0x00000000 dbr=0x00000000 delayed_pc=0x7f692320 fpul=0x00000000
r0=0x00e11158 r1=0x00000000 r2=0x00000001 r3=0x7ffff2e0
r4=0x00e11068 r5=0x7ffff314 r6=0x7ffff31c r7=0x00000000
r8=0x004007b0 r9=0x00000000 r10=0x00000000 r11=0x00000000
r12=0x7f79ac54 r13=0x00000000 r14=0x7ffff288 r15=0x7ffff288
r16=0x00000000 r17=0x00000000 r18=0x00000000 r19=0x00000000
r20=0x00000000 r21=0x00000000 r22=0x00000000 r23=0x00000000
(sid-sh4-sbuild)root@z6:/#
The same code works fine on my Renesas SH7785LCR evaluation board:
root@tirpitz:~> uname -a
Linux tirpitz 3.16.7-ckt7 #8 PREEMPT Fri Oct 21 18:47:41 CEST 2016 sh4a GNU/Linux
root@tirpitz:~> gcc -o setcontext setcontext.c -lpthread
root@tirpitz:~> ./setcontext
root@tirpitz:~> echo $?
0
root@tirpitz:~>
Due to this bug, it is not possible to compile gcc-7 with the Go frontend enabled on qemu-sh4.
This still reproduces on git master:
(sid-sh4-sbuild)root@nofan:/# gcc setcontext.c -o setcontext -lpthread
(sid-sh4-sbuild)root@nofan:/# ./setcontext
Unhandled trap: 0x180
pc=0x7f68e99e sr=0x00000000 pr=0x00400750 fpscr=0x00080000
spc=0x00000000 ssr=0x00000000 gbr=0x7f7a2de8 vbr=0x00000000
sgr=0x00000000 dbr=0x00000000 delayed_pc=0x7f68e960 fpul=0x00000000
r0=0x00e11158 r1=0x00000000 r2=0x00000001 r3=0x7ffff590
r4=0x00e11068 r5=0x7ffff5c4 r6=0x7ffff5cc r7=0x00000000
r8=0x004007f0 r9=0x00000000 r10=0x00000000 r11=0x00000000
r12=0x7f79ec64 r13=0x00000000 r14=0x7ffff538 r15=0x7ffff538
r16=0x00000000 r17=0x00000000 r18=0x00000000 r19=0x00000000
r20=0x00000000 r21=0x00000000 r22=0x00000000 r23=0x00000000
(sid-sh4-sbuild)root@nofan:/#
And it is fixed by reverting 61dedf2af7
(sid-sh4-sbuild)root@nofan:/# ./setcontext
(sid-sh4-sbuild)root@nofan:/# echo $?
0
(sid-sh4-sbuild)root@nofan:/#
So it's presumably the same bug as https://bugs.launchpad.net/qemu/+bug/1796520
The QEMU project is currently considering to move its bug tracking to
another system. For this we need to know which bugs are still valid
and which could be closed already. Thus we are setting older bugs to
"Incomplete" now.
If you still think this bug report here is valid, then please switch
the state back to "New" within the next 60 days, otherwise this report
will be marked as "Expired". Or please mark it as "Fix Released" if
the problem has been solved with a newer version of QEMU already.
Thank you and sorry for the inconvenience.
[Expired for QEMU because there has been no activity for 60 days.]
|