On Wednesday 29 June 2005 03:57 am, Norbert Koch wrote:
> Hello.
>
> I am working on a multi-threaded application which
> may call settimeofday() and therefore may have
> serious problems with timing calculations.
>
> In my applications I calclulate time differences
> using clock_gettime(CLOCK_MONO
On Tue, 27 Jan 2004 01:19:43 +0100, ISAAC GELADO FERNANDEZ <[EMAIL PROTECTED]>
wrote:
- Mensaje original -
De: Jeremy Messenger <[EMAIL PROTECTED]>
Fecha: Miércoles, Octubre 29, 2003 6:33 pm
Asunto: Re: POSIX Threads
On Wed, 29 Oct 2003 13:10:53 +0100, Isaac Gelado <[
- Mensaje original -
De: Jeremy Messenger <[EMAIL PROTECTED]>
Fecha: Miércoles, Octubre 29, 2003 6:33 pm
Asunto: Re: POSIX Threads
> On Wed, 29 Oct 2003 13:10:53 +0100, Isaac Gelado <[EMAIL PROTECTED]> wrote:
>
>
> > But, when the server is running under
On Wed, 29 Oct 2003 13:10:53 +0100, Isaac Gelado <[EMAIL PROTECTED]> wrote:
But, when the server is running under FreeBSD 5.0
I think that you do really need to update your machine to 5.1-CURRENT for
the threads. It's a lot improvement from 5.0, but I have no idea if it
will solve your proble
In the last episode (Oct 30), Isaac Gelado said:
> Dan Nelson escribiÃ:
> >In the last episode (Oct 29), Isaac Gelado said:
> >>This schema is working correctly in a linux machine, so when a
> >>packet is captured an CORBA event is sent to clients. But, when the
> >>server is running under FreeBSD
Dan Nelson escribió:
In the last episode (Oct 29), Isaac Gelado said:
I am developing a distributed application based on MICO (mico-2.3.9),
which uses Packet Capture Library (PCapLib).
In the code, I create a posix thread to execute the pcap_loop
function (this function waits until certain number
In the last episode (Oct 29), Isaac Gelado said:
> I am developing a distributed application based on MICO (mico-2.3.9),
> which uses Packet Capture Library (PCapLib).
>
> In the code, I create a posix thread to execute the pcap_loop
> function (this function waits until certain number of packets
Why don't you either coalesce the events or throttle your send-event
frequency so that it waits a minimum amount of time between sending each
CORBA event. That should make your application more robust and better
able to handle any receive rate you care to throw at it.
As for why it happens.. I don
When the main thread exits, all active threads are immediately
terminated. Since your main subroutine has nothing after the
pthread_create(), it immediately exits, thus your secondary thread has no
chance to run.
Add a delay at the end of the main thread to give the pthread_create() the
time it
> When you say the "new FreeBSD 3.x threads", you mean FreeBSDs default
> libc_r library, not the LinuxThreads library, right?
Correct.
> In what way does your program crash? Have you debugged it? And
> what version of FreeBSD 3.x are you talking about?
I'm running FreeBSD-3.3R, and I'll try
On Thu, 28 Oct 1999, David A. Bader wrote:
>
> I'm familiar with LinuxThreads libc_r that uses BOTH SIGUSR1 and
> SIGUSR2. I recently took code that used to work with FSU's
> implementation of threads under FreeBSD; and instead recompiled with
> the new FreeBSD 3.x threads; however, it crashes n
> I'm familiar with LinuxThreads libc_r that uses BOTH SIGUSR1 and
> SIGUSR2. I recently took code that used to work with FSU's
> implementation of threads under FreeBSD; and instead recompiled with
> the new FreeBSD 3.x threads; however, it crashes now when creating
> threads.
When you say the "
I'm familiar with LinuxThreads libc_r that uses BOTH SIGUSR1 and
SIGUSR2. I recently took code that used to work with FSU's
implementation of threads under FreeBSD; and instead recompiled with
the new FreeBSD 3.x threads; however, it crashes now when creating
threads.
The FSU threads (that used
> I have an application that uses SIGUSR1, but also POSIX threads. It
> appears (?) that the user-level POSIX threads now incorporated into
> FreeBSD 3.x use SIGUSR1 and SIGUSR2. Is this correct? If so, and I
> have a threaded application, what signals are still available for use?
No, the thread
man 3 setvbuf
- ad
> Hi there,
>
> I have written a multithreaded application.
> In which, I have redirected stdin, stdout and stderr to some files.
>
> Does anybody know why if I make a call to fprintf family of functions, I get
> nothing in the output files, until I call fflush?
To Unsubscri
Files are block buffered not line buffered.
Switch on hot piping (sorry, don't know how to), or wait until you have
written 64kb, of flush more often.
Nick
On Tue, 20 Jul 1999, Andrei Iltchenko wrote:
> Hi there,
>
> I have written a multithreaded application.
> In which, I have redirecte
man 3 setvbuf
- ad
> Hi there,
>
> I have written a multithreaded application.
> In which, I have redirected stdin, stdout and stderr to some files.
>
> Does anybody know why if I make a call to fprintf family of functions, I get nothing
>in the output files, until I call fflush?
To Unsubscri
Files are block buffered not line buffered.
Switch on hot piping (sorry, don't know how to), or wait until you have
written 64kb, of flush more often.
Nick
On Tue, 20 Jul 1999, Andrei Iltchenko wrote:
> Hi there,
>
> I have written a multithreaded application.
> In which, I have redirect
18 matches
Mail list logo
