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 116480 - Invalid watches hang debug session
Summary: Invalid watches hang debug session
Status: VERIFIED FIXED
Alias: None
Product: cnd
Classification: Unclassified
Component: Debugger (show other bugs)
Version: 6.x
Hardware: PC Linux
: P2 blocker (vote)
Assignee: _ gordonp
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-09-24 10:13 UTC by radam
Modified: 2009-06-25 10:59 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 radam 2007-09-24 10:13:21 UTC
When you have a (few) watches that can't be resolved in the current context (where the IDE stops on a breakpoint) the
IDE hangs immediately. It seems that the IDE tries to resolve these invalid watches but fails and keeps trying.

OS:
Ubuntu 7.04 on a AMD X2 3800 / 1 GB
Debugger: GDB
Comment 1 Alexander Pepin 2007-09-24 13:19:56 UTC
I cannot reproduce the issue neither on Ubuntu nor on any other platform. Please provide more info about GDB version and
exact steps you performed to reproduce the issue.
Comment 2 _ gordonp 2007-09-24 15:32:42 UTC
Please also provide exact information about which NetBeans 6.0 you're using. Watches have not worked
well and the code has been changing fairly regularly. Knowing which build you are using would help. 
Comment 3 radam 2007-09-25 10:26:50 UTC
I had a piece of code where I could reproduce the bug easily. But after removing some garbage (to send it to here)the
bug only showed up very occasionly. I could not recover the original file. But the few times that I succeeded to
reproduce the freeze it was after enabling en disabling a breakpoint and adding not existent watches (before debugging).
Also after a fresh start of Netbeans I succeeded to reproduce. One time I got a freeze only with a breakpoint. The IDE
freezes right after reaching the breakpoint. If there are watches you see the text 'evaluating'. The position of the
breakpoint is turned green. If I look to the processtree I see that the debugged (console) application is stopped and
the rest of the tree is sleeping. It looks like a deadlock / race condition or a missed signal where the IDE is waiting
for some response. The whole processtree is using no cpu. I will try to make +another good testcase.
Used components:
Netbeans: 6.0 Beta as available for general testing
CND: As in the 6.0 Beta
GDB: GNU gdb 6.6-debian

A procestree when freezed:
- java (sleeping)
-- gdb (sleeping)
--- myconsoleapplication (stopped)
-- gnome-terminal (sleeping)
--- gdb_helper_6162 (sleeping, sometimes toggling to active)
---- sleep (sleeping, appears when gdb_helper toggles to active and disappears after some time, everytime a new proces
is created (procesid is changing constantly))
--- gnome-pty-helper (sleeping)

Comment 4 _ gordonp 2007-09-25 14:39:58 UTC
Please download a current nightly before spending more time trying to duplicate the problem. There
have been too many code changes since Beta1 in Watch code that proof-of-problem in beta1 doesn't
mean the problem hasn't been resolved.

You can get current nightlies at http://bits.netbeans.org/download/6.0/nightly/latest.
Comment 5 radam 2007-09-30 11:24:42 UTC
Could not reproduce the bug anymore with the latest nightly builds.
Comment 6 Alexander Pepin 2007-10-11 15:37:04 UTC
Verified in nightly build 20071010