- From: Tuexen Michael <Michael.Tuexen AT icn.siemens.de>
- To: "'discussion AT sctp.de'" <discussion AT sctp.de>
- Cc: "'Jose, Tinku Malayil'" <tinku.jose AT wipro.com>
- Subject: RE: [SCTP-Discussion] Problems facing in multithreading.
- Date: Thu Jul 11 10:02:01 2002
- List-id: SCTP Discussions <discussion.sctp.de>
Dear Jose,
we are using the sctplib in a multithreaded way in the
socketapi library. We do not support multithreading
in general in the sctplib, but you could have a look
in the implementation of the socketapi lib.
So I would suggest
1. Upgrade to the pre18 version. We fixed a lot of bug since
pre16.
2. Use the socketapi lib which supports multithreading.
Best regards
Michael
Michael Tuexen Tel.: +49 89 722 47210
Siemens AG Fax: +49 89 722 48212
ICN WN CC SE 7 e-Mail:
Michael.Tuexen AT icn.siemens.de
>
-----Original Message-----
>
From: Jose, Tinku Malayil
>
[mailto:tinku.jose AT wipro.com]
>
Sent: Thursday, July 11, 2002 5:52 AM
>
To:
>
discussion AT sctp.de
>
Subject: [SCTP-Discussion] Problems facing in multithreading.
>
>
>
Hi,
>
>
We are using the sctplib (sctplib-1.0.0-pre16) for
>
a multithreaded application. The sctpsend is in one thread
>
whereas the callbacks are in another thread. binary is core dumping
>
randomly because of some synchronization problem (we suspect).
>
>
From the code we understood that it is because of the use of some
>
global variables (currentAssociation in distribution.c).
>
we tried putting locks in send and receive
>
but now we are facing core dump in timer compare. we feel
>
that this is
>
also because of the same reason.
>
>
did anyone face this problem before, then please let us know how
>
u solved it. or is it because of improper usage of the library.
>
>
rgds
>
Jose, Tinku Malayil.
>
>
>
- RE: [SCTP-Discussion] Problems facing in multithreading., Tuexen Michael, 07/11/2002
Archive powered by MHonArc 2.6.19+.