Bug 906 – In NSC TCP socket, when a fork occurs, txbuffersize is not copied

Bug 906 - In NSC TCP socket, when a fork occurs, txbuffersize is not copied


Summary:	In NSC TCP socket, when a fork occurs, txbuffersize is not copied

Status:	RESOLVED FIXED

Product:	ns-3
Classification:	Unclassified
Component:	internet
Version:	pre-release
Hardware:	All All

Importance:	P5 normal
Assigned To:	ns-bugs

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2010-05-04 06:22 UTC by Antti Mäkelä
Modified:	2010-05-29 19:49 UTC (History)
CC List:	1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Antti Mäkelä 2010-05-04 06:22:39 UTC

When a NSC TCP socket is in listening state and accepts a connection, during the for txbuffersize will be uninitialized in the new (forked) socket.

This eventually crashes at Assert on line 367 in GetTxAvailable, since it can be anything.

I added m_txBufferSize = sock.m_txBufferSize; to the copy constructor and problem seems to have gone away.

Comment 1 Tom Henderson 2010-05-29 19:49:23 UTC

changeset: 2b1bbc8d0c58