Exit code 11

[Eddy]

Hi,
After successfully bluiding, I tried to launch the simulation and I
got a red line in the output ended by " exited with code 11"
Where do I can find the signification of exit codes ?

Thnx

--
You received this message because you are subscribed to the Google Groups "ns-3-users" group.
To post to this group, send email to ns-3-...@googlegroups.com.
To unsubscribe from this group, send email to ns-3-users+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/ns-3-users?hl=en.

[Sreedevi Veerathu]

Hai,

Actually i too got same problem while execution. But later when i am running many programs i saw some corrections in the program which i have simulated so after keen observation there will be surely some mistake in the program then you can run the program with out this error. So, with my experience i can give you my suggestion.

Thanks and Regards,
Sreedevi.

[Pavel Boyko]

Hi, Eddy,

On Wed, Apr 21, 2010 at 7:47 PM, Eddy <souf...@gmail.com> wrote:
> After successfully bluiding, I tried to launch the simulation and I
> got a red line in the output ended by " exited with code 11"

This is an obscure way waf uses to report a segmentation fault (your
simulation was killed by signal 11 SIGSEGV for accessing an invalid
address in memory). You should enable core dumps and use debugger to
find the segfault reason.

> Where do I can find the signification of exit codes ?

`man signal` usually contains a table of signals and their numerical
values. Exit codes 11 and 8 (floating point exception) are the most
popular ones.

Good luck,
Pavel

[Eddy]

Hi,
How can I debug a NS 3 program ?

Thnx

[Antti Mäkelä]

On Apr 22, 3:19 pm, Eddy <souf....@gmail.com> wrote:
> Hi,
> How can I debug a NS 3 program ?

Start with ./waf --run yourprog --command-template="gdb %s" to load
it in gdb.

Quick commands:

Type "run" to start execution. When it fails, type "bt" to get
backtrace on where you were going.

Restart, but this time before "run" set breakpoints, e.g. break
mysource.cc:1234 to stop execution at that point. Then you can either
type n or s to step line-by-line through the execution (s steps into
function calls, n does not). You can use 'print varname' to check
contents of variables and pretty much anything else (for class
variables, you might need to use 'print this->classvar').

For more on gdb, google for it.

[Eddy]

Hi,
What's about the compilation error, how can I get more information on
a compilation error ?

Thnx

[Craig Dowell]

> What's about the compilation error, how can I get more information on
> a compilation error ?

google. Seriously. google is your friend.

Compilation errors are not specific to ns-3. If you are going to write
programs, you will have to be able to interpret error messages from your
tools.

[Quincy]

NS3 is mostly just C++, so most websites about debugging C++ programs
will be useful to you.

Quincy