- From: Marc Boucher <marc+sctp AT mbsi.ca>
- To: discussion AT sctp.de
- Subject: Re: [Re: [SCTP-Discussion] echo_server setfaults]
- Date: Thu May 3 11:55:02 2001
- List-id: SCTP Discussions <discussion.sctp.de>
On Tue, May 01, 2001 at 03:39:38PM -0600,
burzum AT usa.net
wrote:
>
Hi Michael,
>
>
Sorry for the lameness - I didn't provide the -s source address ...:))
I think that it is not you but the examples that are in fact pretty lame
for *coredumping* when arguments are missing. This is extremely confusing for
new users. Michael, Andreas: can we fix this?
Marc
>
>
Running with -s source_addr works, but I am unable to test it. I use
>
echo_tool
>
to test. For example:
>
>
terminal1: ./echo_server -s 198.168.1.1 -V
>
terminal2: ./echo_tool -s 198.168.1.2 -s 198.168.1.1 -n 100 -V
>
>
I get the following output:
>
>
terminal1(echo_server):
>
1 : Communication up (1 paths)
>
1 : Communication lost (status 1)
>
>
>
terminal2(echo_tool):
>
1 : Communication lost (status 1)
>
>
Both are run by 'root'. What is the correct way to run the tests??
>
>
Thank you
>
Marsel
>
>
Michael T?xen
>
<Michael.Tuexen AT micmac.franken.de>
>
wrote:
>
Dear Marsel,
>
>
have you supplied at least one source address?
>
>
/echo_server
>
>
will segfault.
>
>
/echo_server -s 192.168.1.1
>
>
should run when started as root (I assume that one of your addresses is
>
192.168.1.1).
>
>
We should check the command line arguments and I will write that stuff for
>
pre11.
>
If you still encounter problems, please do not hesitate to contact us.
>
>
Best regards
>
>
Michael
>
>
--
>
e-mail:
>
Michael.Tuexen AT micmac.franken.de
>
>
On Tue, May 1, 2001,
>
burzum AT usa.net
>
>
<burzum AT usa.net>
>
wrote:
>
>
>Hello all
>
>
>
>Just downloaded the sctplib-1.0.0-pre9. Compiled with not problems under
>
>Linux RH 7.0, but when I try to run echo_server, it segfaults right away.
>
>Running the prog in gdb, shows that the timer list was un-initialized, and
>
it
>
>segfaults when trying to access the list elements. My questions:
>
>1) Does the timer list have to be initialized? The timer is initialized in
>
>the adl_init_adaptation_layer(), but it is apparently not called anywhere.
>
>
>
>2) Has anyone else had this problem?
>
>
>
>Thank you
>
>Marsel
>
>
>
>____________________________________________________________________
>
>Get free email and a permanent address at http://www.netaddress.com/?N=1
>
>_______________________________________________
>
>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
>
>
>
____________________________________________________________________
>
Get free email and a permanent address at http://www.netaddress.com/?N=1
>
_______________________________________________
>
discussion mailing list
>
discussion AT sctp.de
>
http://www.sctp.de/mailman/listinfo/discussion
>
Archive powered by MHonArc 2.6.19+.