Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 10 of 244 for thread1 (0.2 sec)

  1. src/cmd/cgo/internal/test/test.go

    	return 5242;
    }
    
    // issue 5337
    // Verify that we can withstand SIGPROF received on foreign threads
    
    #ifdef WIN32
    void test5337() {}
    #else
    static void *thread1(void *p) {
    	(void)p;
    	pthread_kill(pthread_self(), SIGPROF);
    	return NULL;
    }
    void test5337() {
    	pthread_t tid;
    	pthread_create(&tid, 0, thread1, NULL);
    	pthread_join(tid, 0);
    }
    #endif
    
    // issue 5603
    
    Registered: Wed Jun 12 16:32:35 UTC 2024
    - Last Modified: Mon May 20 15:50:06 UTC 2024
    - 48.5K bytes
    - Viewed (0)
  2. src/runtime/signal_unix.go

    	}
    }
    
    // minitSignalMask is called when initializing a new m to set the
    // thread's signal mask. When this is called all signals have been
    // blocked for the thread.  This starts with m.sigmask, which was set
    // either from initSigmask for a newly created thread or by calling
    // sigsave if this is a non-Go thread calling a Go function. It
    // removes all essential signals from the mask, thus causing those
    Registered: Wed Jun 12 16:32:35 UTC 2024
    - Last Modified: Fri May 10 16:04:54 UTC 2024
    - 45K bytes
    - Viewed (0)
  3. okhttp/src/main/kotlin/okhttp3/internal/concurrent/TaskRunner.kt

      /**
       * When we need a new thread to run tasks, we call [Backend.execute]. A few microseconds later we
       * expect a newly-started thread to call [Runnable.run]. We shouldn't request new threads until
       * the already-requested ones are in service, otherwise we might create more threads than we need.
       *
       * We use [executeCallCount] and [runCallCount] to defend against starting more threads than we
    Registered: Sun Jun 16 04:42:17 UTC 2024
    - Last Modified: Mon Apr 29 00:33:04 UTC 2024
    - 10.6K bytes
    - Viewed (0)
  4. guava/src/com/google/common/util/concurrent/MoreExecutors.java

      }
    
      /**
       * Add a shutdown hook to wait for thread completion in the given {@link ExecutorService service}.
       * This is useful if the given service uses daemon threads, and we want to keep the JVM from
       * exiting immediately on shutdown, instead giving these daemon threads a chance to terminate
       * normally.
       *
       * @param service ExecutorService which uses daemon threads
    Registered: Wed Jun 12 16:38:11 UTC 2024
    - Last Modified: Wed May 15 10:40:05 UTC 2024
    - 43.7K bytes
    - Viewed (0)
  5. android/guava/src/com/google/common/util/concurrent/MoreExecutors.java

      }
    
      /**
       * Add a shutdown hook to wait for thread completion in the given {@link ExecutorService service}.
       * This is useful if the given service uses daemon threads, and we want to keep the JVM from
       * exiting immediately on shutdown, instead giving these daemon threads a chance to terminate
       * normally.
       *
       * @param service ExecutorService which uses daemon threads
    Registered: Wed Jun 12 16:38:11 UTC 2024
    - Last Modified: Wed May 15 10:40:05 UTC 2024
    - 39K bytes
    - Viewed (0)
  6. guava-tests/test/com/google/common/util/concurrent/TestThread.java

        start();
      }
    
      // Thread.stop() is okay because all threads started by a test are dying at the end of the test,
      // so there is no object state put at risk by stopping the threads abruptly. In some cases a test
      // may put a thread into an uninterruptible operation intentionally, so there is no other way to
      // clean up these threads.
      @SuppressWarnings("deprecation")
      @Override
    Registered: Wed Jun 12 16:38:11 UTC 2024
    - Last Modified: Tue Jun 11 16:13:05 UTC 2024
    - 10.8K bytes
    - Viewed (0)
  7. android/guava-tests/test/com/google/common/util/concurrent/TestThread.java

        start();
      }
    
      // Thread.stop() is okay because all threads started by a test are dying at the end of the test,
      // so there is no object state put at risk by stopping the threads abruptly. In some cases a test
      // may put a thread into an uninterruptible operation intentionally, so there is no other way to
      // clean up these threads.
      @SuppressWarnings("deprecation")
      @Override
    Registered: Wed Jun 12 16:38:11 UTC 2024
    - Last Modified: Tue Jun 11 16:13:05 UTC 2024
    - 10.8K bytes
    - Viewed (0)
  8. android/guava-tests/test/com/google/common/util/concurrent/JSR166TestCase.java

      /** Checks that the threads do not terminate within the given millisecond delay. */
      void assertThreadsStayAlive(long millis, Thread... threads) {
        try {
          // No need to optimize the failing case via Thread.join.
          delay(millis);
          for (Thread thread : threads) assertTrue(thread.isAlive());
        } catch (InterruptedException ie) {
          fail("Unexpected InterruptedException");
        }
      }
    
    Registered: Wed Jun 12 16:38:11 UTC 2024
    - Last Modified: Mon Jun 10 19:21:11 UTC 2024
    - 37.7K bytes
    - Viewed (0)
  9. okhttp-testing-support/src/main/kotlin/okhttp3/internal/concurrent/TaskFaker.kt

     * deterministic.
     *
     * This class ensures that at most one thread is running at a time. This is initially the JUnit test
     * thread, which yields its execution privilege while calling [runTasks], [runNextTask], or
     * [advanceUntil]. These functions don't return until the task threads are all idle.
     *
     * Task threads release their execution privilege in these ways:
     *
    Registered: Sun Jun 16 04:42:17 UTC 2024
    - Last Modified: Mon Apr 29 00:33:04 UTC 2024
    - 12.6K bytes
    - Viewed (0)
  10. platforms/software/testing-base-infrastructure/src/main/java/org/gradle/api/internal/tasks/testing/worker/TestWorker.java

     * - {@link RemoteTestClassProcessor#stop()}
     *
     * Commands are received on communication threads and then processed sequentially on the main thread.  Although concurrent calls to
     * any of the methods from {@link RemoteTestClassProcessor} are supported, the commands will still be executed sequentially in the
     * main thread in order of arrival.
     */
    Registered: Wed Jun 12 18:38:38 UTC 2024
    - Last Modified: Tue May 28 15:59:04 UTC 2024
    - 10K bytes
    - Viewed (0)
Back to top