[#3726] Fixnum#clone and Float#clone raise different exceptions — "David A. Black" <dblack@...>

Hi --

15 messages 2004/11/12
[#3749] Re: Fixnum#clone and Float#clone raise different exceptions — "David A. Black" <dblack@...> 2004/11/16

Hi --

[#3751] Re: Fixnum#clone and Float#clone raise different exceptions — Yukihiro Matsumoto <matz@...> 2004/11/16

Hi,

[#3752] Re: Fixnum#clone and Float#clone raise different exceptions — "David A. Black" <dblack@...> 2004/11/16

Hi --

[#3785] The latest 1.8.2 cvs prints parse error when starting extension compiling — Yukihiro Matsumoto <matz@...>

Hi,

13 messages 2004/11/23
[#3787] Re: The latest 1.8.2 cvs prints parse error when starting extension compiling — Johan Holmberg <holmberg@...> 2004/11/23

[ ruby-Bugs-1021 ] problem with break points on non-executable lines

From: noreply@...
Date: 2004-11-04 17:57:51 UTC
List: ruby-core #3688
Bugs item #1021, was opened at 2004-11-04 12:57
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=1698&aid=1021&group_id=426

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Nobody (None)
Assigned to: Nobody (None)
Summary: problem with break points on non-executable lines

Initial Comment:
When I use the Ruby debugger and attempt to define a breakpoint on a non-executable line such as a blank line, it allows me to do that.  The breakpoint is ignored.  I would expect that (a) the debugger should instead set the breakpoint on the next executable line of code and (b) offer a message back to the user (me) to that effect.

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=1698&aid=1021&group_id=426

In This Thread

Prev Next