AuroraMiddleware/glibc
1
0
Fork 0
mirror of https://sourceware.org/git/glibc.git synced 2024-11-08 14:20:07 +00:00
Code Issues Packages Projects Releases Wiki Activity

setcontext: Clarify termination when uc_link is the null pointer.

Browse Source
This commit is contained in:
Thomas Schwinge 2012-07-17 10:05:55 +02:00
parent aaf5420c6d
commit dc97c227c9
3 changed files with 13 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
ChangeLog
View File

@ -1,3 +1,11 @@
2012-07-17 Thomas Schwinge <thomas@codesourcery.com>
Andreas Krebbel <Andreas.Krebbel@de.ibm.com>
* manual/setjmp.texi (setcontext): Clarify normal process
termination when uc_link is the null pointer.
* stdlib/tst-makecontext.c (cf): Exercise this: remove explicit
exit call.
2012-07-16 Andreas Schwab <schwab@linux-m68k.org>
* stdlib/bug-getcontext.c (do_test): Don't test FE_ALL_EXCEPT in

3
manual/setjmp.texi
View File

@ -354,7 +354,8 @@ specified parameters passed. If this function returns execution is
resumed in the context which was referenced by the @code{uc_link}
element of the context structure passed to @code{makecontext} at the
time of the call. If @code{uc_link} was a null pointer the application
terminates in this case.
terminates normally with an exit status value of @code{EXIT_SUCCESS}
(@pxref{Program Termination}).
Since the context contains information about the stack no two threads
should use the same context at the same time. The result in most cases

4
stdlib/tst-makecontext.c
View File

@ -35,7 +35,9 @@ cf (int i)
printf ("i %d thr %d\n", i, thr);
exit (1);
}
exit (0);
/* Since uc_link below has been set to NULL, setcontext is supposed to
terminate the process normally after this function returns. */
}
int