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 61008 - stupid debug of netbeans 4.1
Summary: stupid debug of netbeans 4.1
Status: CLOSED WORKSFORME
Alias: None
Product: javame
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 4.x
Hardware: All All
: P3 blocker (vote)
Assignee: _ kherink
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-07-15 07:54 UTC by evzhy
Modified: 2006-10-23 16:41 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description evzhy 2005-07-15 07:54:25 UTC 
I debug my funny game with netbeans 4.1 + mobility package 4.1 + nokia 7210 sdk
I run ...
It stop in a line, but it has not breakpoint! yes, before I ever set breakpoint
this line, but I have remove it! The stupid debuger still stop in this line!
Comment 1 Martin Ryzl 2005-07-15 09:26:02 UTC 
please, look at Windows | Debugger | Breakpoint if the breakpoint is still
listed there. If so, try to delete it from here. Also have you installed latest
debuggere hotfixes (available at netbeans hotfix autoupdate) - we need this
information to be able to reproduce the problem on identical configuration.
There are many reasons why debugging may be broken - SDK, JDI, NetBeans - your
report will definitely help us to improve the quality, thank you very much.
However, please use more polite expressions in future reports. Thanks.
Comment 2 Martin Ryzl 2005-07-15 11:50:53 UTC 
Evans Zhang wrote:

> Hello,
> Yes, in Windows | Debugger | Breakpoint the breakpoint
> is still listed there, and is enable! And I can click
> the item to jump to that corresponding line in editor.
> I like netbeans, hope you improve it more
> industry-strength, powerful, and cool!

> I seems do not install the hotfix of debugger
>
Comment 3 _ kherink 2005-07-25 03:22:34 UTC 
if you can list steps that will reproduce the issue i will try to fix it, for
now i can't find the problem