[ns] ns.exe versus nstk.exe - debugging

[Micheal Murray]

Hi Basim,

I have found Pedro Vale Estrela's pages to be extremely helpful.
There is a panel of links on the left hand side of his homepage which
provide
invaluable information for beginners and advanced users alike.
http://tagus.inesc-id.pt/~pestrela/ns2/

If you step through the debugging pages here it will give you a great
platform to start
debugging from. The otcl debugging is particularly helpful.
There are also lots of useful tips provided throughout the webpages.

Hope this helps,
Regards,
Micheal

2008/8/8 Basim Javed <basimjaved at gmail.com>

> hello Micheal
>
> could you please guide of how to do debugging and which tools are used. I
> am using ns2.31.
> thanks in advance.
> regards
> basim
>
>
> On Fri, Aug 8, 2008 at 1:14 PM, Micheal Murray <mickmur at gmail.com> wrote:
>
>>
>> Hi all,
>>
>> I have had previous success in debugging ns2 tcl scripts through otcl and
>> C++ debugging,
>> using a combination of ddd, MashInspector in nstk environment, and the tcl
>> debugger.
>>
>> However I have recently found trouble trying to debug with ddd. When I
>> open
>> the ns.exe
>> program I am given the 'no debugging symbols found' reply. However when I
>> open the
>> nstk.exe program I can proceed just fine.
>>
>> The otcl side of debugging is working just fine also.
>> Is there a straightforward explanation for this?
>> Has anyone else encountered this?
>>
>> I have taken the following steps to enable debugging support:
>>        > added "-g" in makefile.in such that
>>                    CFLAGS    += -g $(CCOPT) $(DEFINE)
>>        > added "--enable-symbols" to tcl's configure command in
>> ns-allinone/install
>>        > added "--enable-debug" to tclcl's configure in same file
>>        > configured ns-2 with "--enable-debug" flag as well as
>> "--with-tcldebug"
>>
>> I have also noticed that gdb doesn't like the guard32.dll belonging to
>> Comodo's Firewall (v3).
>> There has been a bug report made on this in the Comodo forum. The only way
>> around it at
>> the minute appears to be disabling guard32.dll.
>>
>> Thanks for your time,
>> Micheal
>>
>
>