comp.programming.threads

• Thread Index

---

• Re: Has pthreads become antiquated?
  • From: Joe Seigh
• Re: using pthreads with fork() in linux
  • From: David Hopwood
• Re: Has pthreads become antiquated?
  • From: Chris Friesen
• Re: Has pthreads become antiquated?
  • From: Maxim Yegorushkin
• Re: Has pthreads become antiquated?
  • From: Drazen Kacar
• Re: using pthreads with fork() in linux
  • From: Elena
• Re: Has pthreads become antiquated?
  • From: Joe Seigh
• Re: using pthreads with fork() in linux
  • From: Maxim Yegorushkin
• Re: using pthreads with fork() in linux
  • From: Elena
• Re: using pthreads with fork() in linux
  • From: Elena
• Re: Has pthreads become antiquated?
  • From: Maxim Yegorushkin
• Re: using pthreads with fork() in linux
  • From: Maxim Yegorushkin
• Re: using pthreads with fork() in linux
  • From: Maxim Yegorushkin
• Re: using pthreads with fork() in linux
  • From: Elena
• Re: Locking an STL-like container
  • From: dhruv
• Re: Help with threads in a win32 service
  • From: Richard
• Re: using pthreads with fork() in linux
  • From: Arnold Hendriks
• Re: using pthreads with fork() in linux
  • From: Arnold Hendriks
• Re: using pthreads with fork() in linux
  • From: Maxim Yegorushkin
• Re: using pthreads with fork() in linux
  • From: Elena
• Re: using pthreads with fork() in linux
  • From: Maxim Yegorushkin
• Re: Has pthreads become antiquated?
  • From: Joe Seigh
• Re: using pthreads with fork() in linux
  • From: Elena
• Re: using pthreads with fork() in linux
  • From: Maxim Yegorushkin
• Re: using pthreads with fork() in linux
  • From: Maxim Yegorushkin
• Re: using pthreads with fork() in linux
  • From: Elena
• Re: using pthreads with fork() in linux
  • From: Elena
• Re: using pthreads with fork() in linux
  • From: Arnold Hendriks
• Re: using pthreads with fork() in linux
  • From: Jelte
• Re: using pthreads with fork() in linux
  • From: Maxim Yegorushkin
• Re: Has pthreads become antiquated?
  • From: Maxim Yegorushkin
• Re: Has pthreads become antiquated?
  • From: Joe Seigh
• using pthreads with fork() in linux
  • From: Elena
• Re: Help with threads in a win32 service
  • From: Eric Jensen
• Re: Help with threads in a win32 service
  • From: matt
• Re: Help with threads in a win32 service
  • From: Jim Langston
• Help with threads in a win32 service
  • From: matt
• Re: Has pthreads become antiquated?
  • From: Chris Thomasson
• Re: Has pthreads become antiquated?
  • From: Maxim Yegorushkin
• Re: when multiple threads are waiting on a mutex, which one will acquire the lock first?
  • From: Joe Seigh
• Re: when multiple threads are waiting on a mutex, which one will acquire the lock first?
  • From: amritanshu
• Re: Has pthreads become antiquated?
  • From: Joe Seigh
• Re: Has pthreads become antiquated?
  • From: Marcin 'Qrczak' Kowalczyk
• Re: Has pthreads become antiquated?
  • From: Joe Seigh
• Re: Has pthreads become antiquated?
  • From: Maxim Yegorushkin
• Re: Has pthreads become antiquated?
  • From: Joe Seigh
• Re: checking return value of pthread_mutex_lock ...
  • From: Maxim Yegorushkin
• Re: Has pthreads become antiquated?
  • From: Maxim Yegorushkin
• Has pthreads become antiquated?
  • From: Joe Seigh
• atomic-ptr-plus status
  • From: Joe Seigh
• Re: Multithreading Component
  • From: Barry Kelly
• Re: Multithreading Component
  • From: yeomanly
• Re: Error in MultiThreaded application
  • From: davids
• Re: output of client thread
  • From: Ulrich Eckhardt
• Re: checking return value of pthread_mutex_lock ...
  • From: Steve Watt
• Re: output of client thread
  • From: roger . faulkner
• Re: Returning local pthread_t object after calling pthread_create()
  • From: Marcin 'Qrczak' Kowalczyk
• output of client thread
  • From: luckybalaji
• checking return value of pthread_mutex_lock ...
  • From: iler . ml
• Returning local pthread_t object after calling pthread_create()
  • From: Alex Vinokur
• Re: Multithreading Component
  • From: Barry Kelly
• Multithreading Component
  • From: yeomanly
• Re: temporary disable thread switching using pthreads
  • From: Martin James
• Re: temporary disable thread switching using pthreads
  • From: davids
• Re: temporary disable thread switching using pthreads
  • From: davids
• Re: temporary disable thread switching using pthreads
  • From: Marcel Müller
• Re: temporary disable thread switching using pthreads
  • From: Marcel Müller
• Re: temporary disable thread switching using pthreads
  • From: Marcel Müller
• Re: temporary disable thread switching using pthreads
  • From: Jedrzej Dudkiewicz
• Re: Error in MultiThreaded application
  • From: Balakv
• Re: temporary disable thread switching using pthreads
  • From: davids
• Re: temporary disable thread switching using pthreads
  • From: Joe Seigh
• Re: temporary disable thread switching using pthreads
  • From: Martin James
• Re: sharing data in .NET
  • From: stevenkobes@xxxxxxxxxxx
• Re: temporary disable thread switching using pthreads
  • From: Marcel Müller
• Re: temporary disable thread switching using pthreads
  • From: Joe Seigh
• Re: temporary disable thread switching using pthreads
  • From: Casper H . S . Dik
• Re: temporary disable thread switching using pthreads
  • From: Marcel Müller
• OT [Re: accessing each pthread's context]
  • From: Paul Pluzhnikov
• Re: accessing each pthread's context
  • From: bcreane
• Re: accessing each pthread's context
  • From: bcreane
• Re: accessing each pthread's context
  • From: Paul Pluzhnikov
• Re: accessing each pthread's context
  • From: davids
• Re: temporary disable thread switching using pthreads
  • From: David Hopwood
• Re: accessing each pthread's context
  • From: bcreane
• Re: accessing each pthread's context
  • From: bcreane
• Re: accessing each pthread's context
  • From: Clifford Heath
• Re: Error in MultiThreaded application
  • From: davids
• Re: accessing each pthread's context
  • From: davids
• Re: temporary disable thread switching using pthreads
  • From: davids
• Re: temporary disable thread switching using pthreads
  • From: Joe Seigh
• temporary disable thread switching using pthreads
  • From: Marcel Müller
• Error in MultiThreaded application
  • From: Balakv
• Re: accessing each pthread's context
  • From: Paul Pluzhnikov
• Re: accessing each pthread's context
  • From: bcreane
• Re: accessing each pthread's context
  • From: Paul Pluzhnikov
• accessing each pthread's context
  • From: bcreane
• Re: Proxy GC ordering revisited
  • From: Joe Seigh
• Re: Proxy GC ordering revisited
  • From: Joe Seigh
• Re: Linux pthreads considered harmful
  • From: Clifford Heath
• Re: Linux pthreads considered harmful
  • From: Chris Friesen
• Re: Using thread.h on Red hat linux 2.4.21-4.ELsmp
  • From: Casper H . S . Dik
• Using thread.h on Red hat linux 2.4.21-4.ELsmp
  • From: Neha
• Re: Linux pthreads considered harmful
  • From: Clifford Heath
• Re: Proxy GC ordering revisited
  • From: Joe Seigh
• Re: Another commerical lock-free library
  • From: Joe Seigh
• Re: Linux pthreads considered harmful
  • From: Chris Friesen
• Re: Linux pthreads considered harmful
  • From: Phil Hobbs
• Re: Linux pthreads considered harmful
  • From: Igmar Palsenberg
• Re: sharing data in .NET
  • From: davids
• Re: sharing data in .NET
  • From: Joe Seigh
• Re: Linux pthreads considered harmful
  • From: Chris Friesen
• Re: Linux pthreads considered harmful
  • From: Phil Hobbs
• sharing data in .NET
  • From: stevenkobes@xxxxxxxxxxx
• Re: Linux pthreads considered harmful
  • From: Chris Friesen
• Re: Linux pthreads considered harmful
  • From: Chris Friesen
• Another commerical lock-free library
  • From: Joe Seigh
• Re: properly destroy and cleanup a thread
  • From: Marcin 'Qrczak' Kowalczyk
• Re: properly destroy and cleanup a thread
  • From: goldfita
• Re: properly destroy and cleanup a thread
  • From: Steve Watt
• Re: properly destroy and cleanup a thread
  • From: goldfita
• Re: properly destroy and cleanup a thread
  • From: Marcin 'Qrczak' Kowalczyk
• properly destroy and cleanup a thread
  • From: goldfita
• Re: Linux pthreads considered harmful
  • From: Phil Hobbs
• ADD WINGS TO YOUR RESUME !!!!!
  • From: Gopi
• Re: pthread_*, errno and POSIX
  • From: Maxim Konovalov
• Re: pthread_*, errno and POSIX
  • From: David Hopwood
• Re: pthread_*, errno and POSIX
  • From: Alexander Terekhov
• Re: pthread_*, errno and POSIX
  • From: Thomas Maier-Komor
• Re: pthread_*, errno and POSIX
  • From: Maxim Konovalov
• Re: pthread_*, errno and POSIX
  • From: Thomas Maier-Komor
• pthread_*, errno and POSIX
  • From: Maxim Konovalov
• Re: Unexpected exit of pthread
  • From: Marcin 'Qrczak' Kowalczyk
• Re: Linux pthreads considered harmful
  • From: Joe Seigh
• Re: Linux pthreads considered harmful
  • From: Joe Seigh
• Re: Linux pthreads considered harmful
  • From: Chris Friesen
• Re: can pipes be used with posix threads
  • From: Giancarlo Niccolai
• Re: Linux pthreads considered harmful
  • From: Giancarlo Niccolai
• Re: Linux pthreads considered harmful
  • From: davids
• Linux pthreads considered harmful
  • From: Phil Hobbs
• Proxy GC ordering revisited
  • From: Joe Seigh
• Re: Unexpected exit of pthread
  • From: Dave Butenhof
• Re: Unexpected exit of pthread
  • From: annamalai . gurusami
• Re: Unexpected exit of pthread
  • From: davids
• Re: Locking an STL-like container
  • From: Torsten Robitzki
• Re: Locking an STL-like container
  • From: dhruv
• Re: Unexpected exit of pthread
  • From: Marcin 'Qrczak' Kowalczyk
• Unexpected exit of pthread
  • From: annamalai . gurusami
• Re: Locking an STL-like container
  • From: Torsten Robitzki
• Re: Locking an STL-like container
  • From: Christian Rössel
• Re: Locking an STL-like container
  • From: Christian Rössel
• Re: mulit-thread's problem
  • From: Gianni Mariani
• Re: Locking an STL-like container
  • From: Andrei Korostelev
• Re: can pipes be used with posix threads
  • From: aston
• mulit-thread's problem
  • From: DaVinci
• can pipes be used with posix threads
  • From: chaithra . b
• Re: MULTITHREADED
  • From: Joe Seigh
• Re: MULTITHREADED
  • From: aston
• Re: pthread_key_create() destructor always called?
  • From: Frank Cusack
• Re: pthread_key_create() destructor always called?
  • From: davids
• Re: MULTITHREADED
  • From: davids
• Re: thread id range?
  • From: davids
• Re: pthread_key_create() destructor always called?
  • From: Patrick TJ McPhee
• thread id range?
  • From: Frank Cusack
• pthread_key_create() destructor always called?
  • From: Frank Cusack
• Re: Locking an STL-like container
  • From: Torsten Robitzki
• Locking an STL-like container
  • From: Christian Rössel
• Re: MULTITHREADED
  • From: aston
• Re: when multiple threads are waiting on a mutex, which one will acquire the lock first?
  • From: Joe Seigh
• Re: MULTITHREADED
  • From: Joe Seigh
• MT-safe observer pattern impl ideas
  • From: somedeveloper
• Re: when multiple threads are waiting on a mutex, which one will acquire the lock first?
  • From: Ian Collins
• MULTITHREADED
  • From: aston
• Re: when multiple threads are waiting on a mutex, which one will acquire the lock first?
  • From: davids
• RFC - New Object-Oriented Method of Parallel Programming
  • From: Slawomir J.
• Re: Need embedded language
  • From: stephanearnold
• Re: Problem with function pointer
  • From: Sohail Ahmed Siddiqui
• Re: Problem with function pointer
  • From: Ulrich Eckhardt
• Re: when multiple threads are waiting on a mutex, which one will acquire the lock first?
  • From: Ben Pfaff
• Re: when multiple threads are waiting on a mutex, which one will acquire the lock first?
  • From: Joe Seigh
• Re: when multiple threads are waiting on a mutex, which one will acquire the lock first?
  • From: Ben Pfaff
• Re: when multiple threads are waiting on a mutex, which one will acquire the lock first?
  • From: Joe Seigh
• Re: when multiple threads are waiting on a mutex, which one will acquire the lock first?
  • From: David Hopwood
• Re: when multiple threads are waiting on a mutex, which one will acquire the lock first?
  • From: Joe Seigh
• Re: when multiple threads are waiting on a mutex, which one will acquire the lock first?
  • From: gottlobfrege
• Re: when multiple threads are waiting on a mutex, which one will acquire the lock first?
  • From: Alex
• Re: when multiple threads are waiting on a mutex, which one will acquire the lock first?
  • From: Alex
• Re: when multiple threads are waiting on a mutex, which one will acquire the lock first?
  • From: Joe Seigh
• Re: when multiple threads are waiting on a mutex, which one will acquire the lock first?
  • From: Alex
• Re: Problem with function pointer
  • From: Sohail Ahmed Siddiqui
• Re: Problem with function pointer
  • From: Sohail Ahmed Siddiqui
• Re: Need embedded language
  • From: gottlobfrege
• Re: when multiple threads are waiting on a mutex, which one will acquire the lock first?
  • From: Eric Sosman
• Need embedded language
  • From: Dale Pippert
• Re: when multiple threads are waiting on a mutex, which one will acquire the lock first?
  • From: Joe Seigh
• Re: when multiple threads are waiting on a mutex, which one will acquire the lock first?
  • From: Alexander Terekhov
• when multiple threads are waiting on a mutex, which one will acquire the lock first?
  • From: shengwang08
• Re: Problem with function pointer
  • From: Ulrich Eckhardt
• Re: Problem with function pointer
  • From: Sohail Ahmed Siddiqui
• Re: Problem with function pointer
  • From: Philippe Amarenco
• Problem with function pointer
  • From: Sohail Ahmed Siddiqui
• Re: Can we use Message Queue for communication between POSIX threads (pthread)?
  • From: Steve Watt
• Can we use Message Queue for communication between POSIX threads (pthread)?
  • From: youpak2000
• Re: Why this pthread C program blocks?
  • From: Patrick TJ McPhee

We are proud to have Web Hosting and Rack Housing from 9 Net Avenue Deutschland.
(15)