Bug 2022 – spurious characters in config paths

Bug 2022 - spurious characters in config paths


Summary:	spurious characters in config paths

Status:	RESOLVED FIXED

Product:	ns-3
Classification:	Unclassified
Component:	documentation
Version:	pre-release
Hardware:	PC Linux

Importance:	P5 normal
Assigned To:	Tom Henderson

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2014-11-21 14:45 UTC by Tom Henderson
Modified:	2014-12-09 20:24 UTC (History)
CC List:	2 users (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 Tom Henderson 2014-11-21 14:45:13 UTC

Doxygen introspection of config paths is inserting extra '%' characters that are not handled by the config parser.  For instance, this path is reported by the Doxygen to get to the AODV RoutingProtocol.

/NodeList/[i]/$%ns3::%aodv::%RoutingProtocol

in an example program, this path:

/NodeList/0/$%ns3::%aodv::%RoutingProtocol/NetDiameter

 will generate this runtime error:

assert failed. cond="uid != 0", msg="Assert in TypeId::LookupByName: %ns3::%aodv::%RoutingProtocol not found", file=../src/core/model/type-id.cc, line=560
terminate called without an active exception

This path, however, will work:

/NodeList/0/$ns3::aodv::RoutingProtocol/NetDiameter

Comment 1 Peter Barnes 2014-12-03 18:30:18 UTC

Patch pushed r5a41f780e361

http://code.nsnam.org/ns-3-dev/rev/5a41f780e361

Comment 2 Peter Barnes 2014-12-03 18:31:01 UTC

Assigned to Tom to regenerate the Doxygen for our past releases, before closing this bug.

Comment 3 Tom Henderson 2014-12-09 20:24:02 UTC

I found that this did not affect earlier releases; I regenerated Doxygen for ns-3.21 release anyway to pick up some fixes that have occurred since that release was made.