No backtrace in output windows while debugging

View: New views
4 Messages — Rating Filter:   Alert me  

No backtrace in output windows while debugging

by zwadar :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


Hi,

I've just upgraded from 6.1 to 6.5 and updated ruby-debug-base to 0.10.3 and ruby-debug-ide to 0.3.3. (from versions recommanded for usage with 6.1).

With these versions there is no backtrace in outout window when my ruby app crashes.



When I run simple error script



8.reverse



with debugger, in output window is only



Fast Debugger (ruby-debug-ide 0.3.3) listens on localhost:2445



if I just "Run"  the script, backtrace is there



test.rb:1: undefined method `reverse' for 8:Fixnum (NoMethodError)



Am I doing something wrong, or it is a feature of NB6.5 (or maybe ruby-debug-base? ), or it is a bug?



I know, that setting $DEBUG = true will help a littlebit, but with this enabled a lot of llibraries spams a lot to output window, and this is not what I want...



Also when execution of script stops on brakpoint,  NB task in taskbar don't blink as in 6.1, what is confusing...



Tested on Ruby 1.8.6 and 1.8.7, WinXP and Vista 32.






---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...


Re: No backtrace in output windows while debugging

by Martin Krauskopf :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

zwadar wrote:
> Hi,
>
> I've just upgraded from 6.1 to 6.5 and updated ruby-debug-base to 0.10.3 and ruby-debug-ide to 0.3.3. (from versions recommanded for usage with 6.1).
>
> With these versions there is no backtrace in outout window when my ruby app crashes.
[...]
> Am I doing something wrong, or it is a feature of NB6.5 (or maybe ruby-debug-base? ), or it is a bug?

Hi,

yes it is a bug. I've did not get to it yet. It works with JRuby, so I
guess there will be some differences between ruby-debug-base and
ruby-debug-base-java, since upper layers are the same.

   http://www.netbeans.org/issues/show_bug.cgi?id=156118

[...]
> Also when execution of script stops on brakpoint,  NB task in taskbar don't blink as in 6.1, what is confusing...

Right, might be due to migration to new API. I'll take a look at this.
Thanks for the catch. (filing issue for this is welcomed).

        m.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...


Re: No backtrace in output windows while debugging

by Martin Krauskopf :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Martin Krauskopf wrote:

> zwadar wrote:
>> Hi,
>>
>> I've just upgraded from 6.1 to 6.5 and updated ruby-debug-base to
>> 0.10.3 and ruby-debug-ide to 0.3.3. (from versions recommanded for
>> usage with 6.1).
>>
>> With these versions there is no backtrace in outout window when my
>> ruby app crashes.
> [...]
>> Am I doing something wrong, or it is a feature of NB6.5 (or maybe
>> ruby-debug-base? ), or it is a bug?
>
> Hi,
>
> yes it is a bug. I've did not get to it yet. It works with JRuby, so I
> guess there will be some differences between ruby-debug-base and
> ruby-debug-base-java, since upper layers are the same.
>
>   http://www.netbeans.org/issues/show_bug.cgi?id=156118

Was bug in the ruby-debug-ide. I've fixed it there. So all you need is
to upgrade ruby-debug-ide to either 0.3.4 for NetBeans 6.5, or 0.4.4 for
NetBeans 7.0 (through gem tool or directly[1])

Let me know if it does not work for you.

Thanks,
        m.

PS: it might take awhile until gems are propagated to rubyforge.org

[1] https://rubyforge.org/frs/?group_id=3085

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...


No backtrace in output windows while debugging

by zwadar :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


fix confirmed, thank you!






---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...