This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 102506 - [DEBUGGER] NPE from o.n.m.ruby.debugger.EditorUtil
Summary: [DEBUGGER] NPE from o.n.m.ruby.debugger.EditorUtil
Status: RESOLVED FIXED
Alias: None
Product: ruby
Classification: Unclassified
Component: Code (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Martin Krauskopf
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-04-25 15:59 UTC by Tomas Danek
Modified: 2007-07-03 14:43 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tomas Danek 2007-04-25 15:59:34 UTC
NetBeans IDE Dev (Build 070425)
1.5.0_10; Java HotSpot(TM) Client VM 1.5.0_10-b02
Windows XP version 5.1 running on x86
en_US (nb); Cp1252
-------------------------
happend during performing steps in issue 102505, after doubleclick on frame with
javasupport.rb:386 in call stack

java.lang.NullPointerException
	at org.netbeans.modules.ruby.debugger.EditorUtil.showLine(EditorUtil.java:154)
	at
org.netbeans.modules.ruby.debugger.model.CallStackModel.performDefaultAction(CallStackModel.java:147)
	at
org.netbeans.spi.viewmodel.Models$DelegatingNodeActionsProvider.performDefaultAction(Models.java:2035)
	at
org.netbeans.spi.viewmodel.Models$CompoundModel.performDefaultAction(Models.java:2296)
	at
org.netbeans.modules.viewmodel.TreeModelNode$1.actionPerformed(TreeModelNode.java:179)
	at org.openide.explorer.view.TreeView$PopupSupport.mouseClicked(TreeView.java:1396)
...
Comment 1 Martin Krauskopf 2007-05-05 18:14:51 UTC
Yes, that's quite possible, since passed line is often obtained with
EditorUtil.getLine() which might return null. Thanks for the catch.

Checking in debugger/src/org/netbeans/modules/ruby/debugger/EditorUtil.java;
new revision: 1.3; previous revision: 1.2
Comment 2 Jiri Kovalsky 2007-07-03 13:59:55 UTC
Reassigning this issue to newly created 'ruby' component.
Comment 3 Jiri Kovalsky 2007-07-03 14:43:13 UTC
Changing target milestone of all resolved Ruby issues from TBD to 6.0 Beta 1 build.