Difference between revisions of "Troubleshooting"
From Nsnam
(tip on non-standard link paths) |
(document cygwin linker noise) |
||
| Line 7: | Line 7: | ||
=== Cygwin === | === Cygwin === | ||
Python bindings do not build successfully due to a gccxml bug. See the [[NS-3_Python_Bindings#Caveats]] page. | Python bindings do not build successfully due to a gccxml bug. See the [[NS-3_Python_Bindings#Caveats]] page. | ||
| + | |||
| + | If you see "resolving vtable" messages while linking such as the below when you compile on Cygwin, you can safely ignore them: | ||
| + | |||
| + | <pre> | ||
| + | [530/535] cxx_link: build/debug/examples/wifi-wired-bridging_23.o -> build/debug | ||
| + | /examples/wifi-wired-bridging.exe | ||
| + | Info: resolving vtable for ns3::EmptyAttributeValueby linking to __imp___ZTVN3ns | ||
| + | 319EmptyAttributeValueE (auto-import) | ||
| + | Info: resolving vtable for ns3::RandomVariableValueby linking to __imp___ZTVN3ns | ||
| + | 319RandomVariableValueE (auto-import) | ||
| + | Info: resolving vtable for ns3::RectangleValueby linking to __imp___ZTVN3ns314Re | ||
| + | ctangleValueE (auto-import) | ||
| + | Info: resolving vtable for ns3::TimeValueby linking to __imp___ZTVN3ns39TimeValu | ||
| + | eE (auto-import) | ||
| + | Info: resolving vtable for ns3::BooleanValueby linking to __imp___ZTVN3ns312Bool | ||
| + | eanValueE (auto-import) | ||
| + | |||
| + | etc. | ||
| + | </pre> | ||
== General build problems == | == General build problems == | ||
Revision as of 22:41, 31 October 2008
Main Page - Current Development - Developer FAQ - Tools - Related Projects - Project Ideas - Summer Projects
Installation - Troubleshooting - User FAQ - HOWTOs - Samples - Models - Education - Contributed Code - Papers
This is a wiki; if you find items not adequately covered below, please consider adding an entry.
Contents
Platform-specific issues
Cygwin
Python bindings do not build successfully due to a gccxml bug. See the NS-3_Python_Bindings#Caveats page.
If you see "resolving vtable" messages while linking such as the below when you compile on Cygwin, you can safely ignore them:
[530/535] cxx_link: build/debug/examples/wifi-wired-bridging_23.o -> build/debug /examples/wifi-wired-bridging.exe Info: resolving vtable for ns3::EmptyAttributeValueby linking to __imp___ZTVN3ns 319EmptyAttributeValueE (auto-import) Info: resolving vtable for ns3::RandomVariableValueby linking to __imp___ZTVN3ns 319RandomVariableValueE (auto-import) Info: resolving vtable for ns3::RectangleValueby linking to __imp___ZTVN3ns314Re ctangleValueE (auto-import) Info: resolving vtable for ns3::TimeValueby linking to __imp___ZTVN3ns39TimeValu eE (auto-import) Info: resolving vtable for ns3::BooleanValueby linking to __imp___ZTVN3ns312Bool eanValueE (auto-import) etc.
General build problems
- Q. What is this kind of build error representative of?
assert failed. file=../src/core/type-id.cc, line=389, cond="uid != 0" Command ['/ns-3-dev/build/debug/examples/mixed-wireless'] exited with code -5
- A. The system can't find the specified TypeId. Check spelling, and whether it is prefixed with the namespace "ns3::"
- Q. A required software package is in a non-standard place. How to get waf to find the packages?
- A. To compile with non-standard link path, use the environment variable LINKFLAGS. Example for bash shell:
LINKFLAGS="-L/tmp" ./waf configure
Run-time errors
- Q. What is this assertion indicating?
assert failed. file=debug/ns3/tags.h, line=105, cond="sizeof (T) <= Tags::SIZE"
- A. The packet tag may be greater than Tags::SIZE (16 bytes)
Debugging tips
- Q. Is there a way to dereference a Ptr when in gdb?
- A. yes: p *ptr->m_ptr
