Exceptions not going to output winndow

[djlewis]

Uncaught exceptions are not going to my output window when debugging.  The run just dies with no report of which line, what exception or the usual stack traceback.

This used to work fine; now it doesn't, in NB 6.1 or 6.5.  I'm using the native Ruby platform, 1.8.6-p111. It does work fine JRuby.

Just to double-check, the exception ~is~ reported when running the same code from the command line, outside NB.  Also, normal output (like from puts) is still going to the output window.  Even an explicit "raise NameError" does not send the output to the output window.

On another system this is fine.  I guess I should try reinstalling NB, but is there someplace to look to see if this got configured wrong?

I'm on Win XP Pro

Thanks.  --David.

[Erno Mononen]

Hi David,

I think you're facing the same issue as in this thread:
http://www.nabble.com/No-backtrace-in-output-windows-while-debugging-td21181320.html

So the bug is in ruby-debug-ide, you need to upgrade it -- see Martin
Krauskopf's second comment in the thread.

HTH,
Erno


djlewis wrote:

> Uncaught exceptions are not going to my output window when debugging.  The
> run just dies with no report of which line, what exception or the usual
> stack traceback.
>
> This used to work fine; now it doesn't, in NB 6.1 or 6.5.  I'm using the
> native Ruby platform, 1.8.6-p111. It does work fine JRuby.
>
> Just to double-check, the exception ~is~ reported when running the same code
> from the command line, outside NB.  Also, normal output (like from puts) is
> still going to the output window.  Even an explicit "raise NameError" does
> not send the output to the output window.
>
> On another system this is fine.  I guess I should try reinstalling NB, but
> is there someplace to look to see if this got configured wrong?
>
> I'm on Win XP Pro
>
> Thanks.  --David.
>  

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

[djlewis]

Thanks -- that fixed it!

BTW, I did search, but only on "exception" plus "output window".  Unfortunately, the relevant post referred to "traceback" but not "exception". I think there's a moral in there somewhere.

--David

Erno Mononen wrote:

Hi David,

I think you're facing the same issue as in this thread:
http://www.nabble.com/No-backtrace-in-output-windows-while-debugging-td21181320.html

So the bug is in ruby-debug-ide, you need to upgrade it -- see Martin
Krauskopf's second comment in the thread.

HTH,
Erno


djlewis wrote:
> Uncaught exceptions are not going to my output window when debugging.  The
> run just dies with no report of which line, what exception or the usual
> stack traceback.
>
> This used to work fine; now it doesn't, in NB 6.1 or 6.5.  I'm using the
> native Ruby platform, 1.8.6-p111. It does work fine JRuby.
>
> Just to double-check, the exception ~is~ reported when running the same code
> from the command line, outside NB.  Also, normal output (like from puts) is
> still going to the output window.  Even an explicit "raise NameError" does
> not send the output to the output window.
>
> On another system this is fine.  I guess I should try reinstalling NB, but
> is there someplace to look to see if this got configured wrong?
>
> I'm on Win XP Pro
>
> Thanks.  --David.
>  


---------------------------------------------------------------------
To unsubscribe, e-mail: [e-mail]
For additional commands, e-mail: [e-mail]