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.
With this build, the gdb startup seems to be a little different, but I get no terminal output, the app appears to be started under gdb (here the ps output): 23294 pts/1 ts+ 0:00 /home/toddb/src/src1/omneon/pcapps/mediareader/obj.linux64/mediareader ...which shows that the process is stopped. But in the ide, the stop and pause button are highlighted as if it is running. If I select console type = internal terminal, I get a new pane in the output window, but no output. All other console types show nothing (this is just a tty app). If I start gdb from the command line using the same binary, it does what I expect. This definitely was not broken with netbeans-trunk-nightly-201010120000-linux.sh The build I am using is: Product Version: NetBeans IDE Dev (Build nbms-and-javadoc-5919-on-101012) Java: 1.6.0_18; Java HotSpot(TM) 64-Bit Server VM 16.0-b13 System: Linux version 2.6.34.7-56.fc13.x86_64 running on amd64; UTF-8; en_US (nb) Userdir: /home/toddb/.netbeans/dev
It was kind of expected regressions due to switching to new common debugger infrastructure. Terminal output now is fixed in bug #191464 Debugger hangs on Linux x64 and on Windows.
On Windows if MinGW+MSYS are used
on some platforms gdb produce *stopped messages without token prefix
fixed in: http://hg.netbeans.org/cnd-main/rev/80e03d6990d8
Integrated into 'main-golden', will be available in build *201011110000* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main/rev/80e03d6990d8 User: Egor Ushakov <gorrus@netbeans.org> Log: fixed #191748 (gdb hangs)
*** Bug 191724 has been marked as a duplicate of this bug. ***
*** Bug 191695 has been marked as a duplicate of this bug. ***
Todd, do you consider the bug fixed in the recent development builds? Thanks!
Sorry, I haven't had a chance to test it... I've been debugging a shared object (which can't easily be debugged under netbeans... a different bug). I'll try to get to it tomorrow or monday.