commit-hurd
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[hurd,commited] hurd: Make sure signals get started


From: Samuel Thibault
Subject: [hurd,commited] hurd: Make sure signals get started
Date: Fri, 13 Nov 2020 11:24:38 +0100

Now that _hurd_libc_proc_init is idempotent, we can always call it,
independently of the __libc_multiple_libcs test which may not match
whether signals should be started or not.
---
 sysdeps/mach/hurd/i386/init-first.c | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/sysdeps/mach/hurd/i386/init-first.c 
b/sysdeps/mach/hurd/i386/init-first.c
index a3d2fdaba0..1827479f86 100644
--- a/sysdeps/mach/hurd/i386/init-first.c
+++ b/sysdeps/mach/hurd/i386/init-first.c
@@ -58,14 +58,14 @@ posixland_init (int argc, char **argv, char **envp)
 {
   __libc_multiple_libcs = &_dl_starting_up && !_dl_starting_up;
 
+  /* Now we have relocations etc. we can start signals etc.  */
+  _hurd_libc_proc_init (argv);
+
   /* Make sure we don't initialize twice.  */
   if (!__libc_multiple_libcs)
     {
       /* Set the FPU control word to the proper default value.  */
       __setfpucw (__fpu_control);
-
-      /* Now we have relocations etc. we can start signals etc.  */
-      _hurd_libc_proc_init (argv);
     }
   else
     {
-- 
2.28.0




reply via email to

[Prev in Thread] Current Thread [Next in Thread]