SCTP Discussions

Text archives Help


[SCTP-Discussion] a weird bug (segmentation fault)


Chronological Thread 
  • From: "Julio Kriger" <juliokriger AT gmail.com>
  • To: discussion AT sctp.de
  • Subject: [SCTP-Discussion] a weird bug (segmentation fault)
  • Date: Mon May 22 09:32:04 2006
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=m28u71BtUbolGFUEvpi9kp8Va+PcyYXIfmM5CBZ0yEmoN+XtecbJu0aum5w++8eD3elEPkRsT6zWqALYrC3Isj48QbIH/tAUrFx1mXt9XdjV5dxKKsUlzbztt0Ii9qmkT4/BVuZT5HVa4m4iPYRUGVna7fTQowrNAT58TrjTRKw=
  • List-id: SCTP Discussions <discussion.sctp.de>

Hi!
I have program that launch 4 threads, each thread open a SCTP connection to another PC. And a weird bug present (actually is a segmentation fault). Here is some code;

    sctpInstance = SCTP_registerInstance(cp->sourcePort, inputStreams, outputStreams, noOfLocalAddresses, localAddressList, LLServerEchoUlp);

        //sleep(5);

        SCTP_associate(sctpInstance, outputStreams, destinationAddress, cp->destPort, clientParamIndex);

If I don't put the "sleep", everyhing works good. But ...

If I put the "sleep" for 10 seconds (on each thread) I get a core dump:

(gdb) down
#0  0xb7ef8c82 in scu_associate (noOfOutStreams=1, noOfInStreams=1, destinationList=0x1, numDestAddresses=1, withPRSCTP=1) at SCTP-control.c:399
(gdb) Quit
(gdb) Quit
(gdb)

Does anyone has an idea why this happens? I'm working with version 1.0.3. Ths bug if fixed on 1.0.4 ?

Regards,
Julio

--
--
Stewie: [After Lois tries to feed Stewie his broccoli "airplane style"] Damn you, Damn the Broccoli, and Damn the Wright Brothers.
----------------------------
Julio Kriger
mailto: juliokriger AT gmail.com



Archive powered by MHonArc 2.6.19+.

Top of page