Chronological Thread 

< Chronological >      < Thread >

---

Folks,

I do call sctp_registerInstance()(Thank you for the tip, Wolfgang) but
something goes wrong during the execution of the code within that function.
I was able to trace it back to all the conversions from union sockunion to
unsigned char(done in my own code) which is then converted back(in the SCTP
library) (but only taking into account the IP address itself, not family
field or other fields) unsigned char to sin.sin_addr. unfortunaly in my
character array, the whole sockunion struct is given not the 32 ipv4 address
only, so the nice conversion routine inet_aton tells(located in
adl_str2sockunion) me: sorry, conversion didn't work, thus skipping the rest
of sctp_registerInstance and ultimatly giving me the segment fault(well we
are not sure, we are only at the start of our troubles :-))

So the question is now:
- should the char array only contain the part needed for sin.sin_addr(= the
IP pointcode address) or should it include more?
- ain't it better to work with the sockunion struct instead of the char/byte
array. At least the compiler get something more to do than generating
assember code. It can warn you if you did provide the wrong parameter to
your function. (I like strong type checking anyway by a compiler)

Thank you for the support.

yours sincerly,
Lode

Siemens Atea ICN D CS D
Software Development
Atealaan 34
B-2200 Herentals Belgium
Tel +32-14-25-2081 / Fax +32-14-25-3212
E-mail:
lode.coene AT siemens.atea.be



> -----Original Message-----
> From: Schruefer Wolfgang
> [mailto:Wolfgang.Schruefer AT icn.siemens.de]
> Sent: dinsdag 3 april 2001 9:54
> To:
> 'discussion AT sctp.de'
> Subject: AW: [SCTP-Discussion] Is the timer_list initialised?
>
>
> Dear Lode
>
> we observed problems like you when we went into the eventLoop
> without calling sctp_registerInstance() before.
> As I understand the code, the function
> sctp_registerInstance() must be the very first SCTP-function
> called by ULP because the general initialisation is done there.
>
> Viele Gruesse
> Wolfgang
>
> **************************************
> Wolfgang Schrüfer SIEMENS AG
> ICN WN CC EKJ 14 TEL: 722-61646
> mailto:Wolfgang.Schruefer AT icn.siemens.de
> **************************************
>
> > -----Ursprüngliche Nachricht-----
> > Von: Coene Lode
> > [SMTP:Lode.Coene AT siemens.atea.be]
> > Gesendet am: Montag, 2. April 2001 18:53
> > An: SCTP Discussion (E-mail)
> > Betreff: [SCTP-Discussion] Is the timer_list initialised?
> >
> > Folks,
> >
> > I've tried to make the SCTP_eventloop work in my code and now i get
> > everytime a Segementation fault. After firing up GDB, I
> found out that is
> > was located in the sctp_eventloop, during function call to
> > get_msecs_to_nexttimer, DLL_IsListEmpty.
> > Input to DLL_IsListEmpty is (0x00) which then leads to the
> segement fault.
> > This looks like a uninitialised pointer(it should point to
> NULL or at least
> > one element should be in the list because it makes a check
> not to the
> > pointer but to pointer->head(which in the present situation
> is clearly "A
> > bridge too far", even when the pointer itself was NULL))
> >
> > BTW is 0x00 equivalent to NULL or it that dependent on OS
> representation.
> >
> > I noticed that there was also a init_timer_list functions,
> but that as far
> > as I can see , not a single line of code in SCTP does call
> that function to
> > initialise the timer_list.
> >
> > So my question is:
> > - did I forget something in my code for initialising
> (looked in the examples
> > didn't bring up anything this far)?
> > - might there be a error in the SCTP lib?
> >
> > Help is always gratefully accepted. Thanks in advance.
> >
> > yours sincerly,
> > Lode
> >
> > Siemens Atea ICN D CS D
> > Software Development
> > Atealaan 34
> > B-2200 Herentals Belgium
> > Tel +32-14-25-2081 / Fax +32-14-25-3212
> > E-mail:
> > lode.coene AT siemens.atea.be
> >
> > _______________________________________________
> > discussion mailing list
> > discussion AT sctp.de
> > http://www.sctp.de/mailman/listinfo/discussion
> _______________________________________________
> discussion mailing list
> discussion AT sctp.de
> http://www.sctp.de/mailman/listinfo/discussion
>

---

• [SCTP-Discussion] Is the timer_list initialised?, Coene Lode, 04/02/2001
  • <Possible follow-up(s)>
  • RE: [SCTP-Discussion] Is the timer_list initialised?, Coene Lode, 04/04/2001
    • Re: [SCTP-Discussion] Is the timer_list initialised?, Andreas Jungmaier, 04/04/2001
  • RE: [SCTP-Discussion] Is the timer_list initialised?, Coene Lode, 04/04/2001
    • Re: [SCTP-Discussion] Is the timer_list initialised?, Marc Boucher, 04/05/2001
      • Re(2): [SCTP-Discussion] Is the timer_list initialised?, Michael Tüxen, 04/05/2001
        • Re: Re(2): [SCTP-Discussion] Is the timer_list initialised?, Marc Boucher, 04/05/2001
      • Re: [SCTP-Discussion] Is the timer_list initialised?, Andreas Jungmaier, 04/05/2001
        • Re: [SCTP-Discussion] Is the timer_list initialised?, Marc Boucher, 04/05/2001
          • [SCTP-Discussion] Strings vs. Sockunion, Andreas Jungmaier, 04/05/2001
  • RE: [SCTP-Discussion] Is the timer_list initialised?, Wagner, Joel, 04/05/2001
    • Re: [SCTP-Discussion] Is the timer_list initialised?, Marc Boucher, 04/05/2001

---

Archive powered by MHonArc 2.6.19+.