Thanks for the comments. I am using a relatively small simulation, but I had
been tracing all events, so I will try your suggestions.
On 7/12/06 12:30 PM, "Pedro Vale Estrela" <[EMAIL PROTECTED]> wrote:
>
> Hi
>
> I also have a fairly poor performance during my otcl debug sessions
> regarding managing the object inspector itself. For this, I just stop the
> simulation at run time, check the objects that I want, check the private
> variables, and find the bug.
>
> For debugging, I have my simulation script parametized to generate a smaller
> and simpler scenario to have to deal with less otcl objects. For C++
> debugging, it greatly helps disabling all the traces to deal with less C++
> objects.
>
> With the debugger turned off, the simulation runs at full speed.
>
> I assume you followed the instructions here:
> http://tagus.inesc-id.pt/~pestrela/ns2/ns2_debugging2.html
I did, and...
> Did you find any difficulties?
None at all!
> Pedro Estrela
>
>
>> -----Original Message-----
>> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
>> Of Brad Montgomery
>> Sent: quarta-feira, 12 de Julho de 2006 17:54
>> To: [email protected]
>> Subject: [ns] Mash Inspector on Mac OS X
>>
>>
>> Hello All,
>>
>> I've recently patched my installation of ns-allinone-2.29 (running on Mac
>> OS
>> 10.4.7) to use the Mash Inspector, but I am experiencing very poor
>> performance.
>>
>> Is anyone else using Mash on Mac OS X?
>>
>> Thanks!
>> Brad
>
>
