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.
Hello, I am an embedded developer, and I am using a lot NCurses, and Netbeans has a very annoying bug with NCurses. What I want to do: - Open a serial port - Draw a GUI with NCurses on it The application is working very fine if I run it without debugger, and if I run it with gdb from a terminal. But when I want to debug it with Netbeans, then NCurses is simply broken, the GUI OVER the serial port is unusable. (I tried to launch the application on the PC (without the serial port), and it is broken too.) To reproduce the bug, create a new project and paste the code snippet from: http://tldp.org/HOWTO/NCURSES-Programming-HOWTO/menus.html (juste add -lncurses and -lmenu to the linker flag) Did not find out how to solve the problem, currently I am using gdb and it is horrible :( Regards, Damien
Also : - CentOS 5.4 - gdb 6.8 - gcc 4.1.2
please attach gdblog (http://wiki.netbeans.org/GdbLog)
example from http://tldp.org/HOWTO/NCURSES-Programming-HOWTO/menus.html works perfectly on windows, I do not have CentOS here, so waiting for gdblog for more details
Created attachment 97345 [details] gdblog Here is the gdblog Regards
thanks, analyzing... just in case, please try to debug it in output window (set project properties/run/console type -> output window)
output window will make it worse, do not try it :)
From the log it looks like debugger started correctly. What did you see in the terminal? Did application respond? I tried it and on my machine (solaris) it starts the debug session by on any keyboard event gdb receives (and catches) a signal, so it is not easy to do any real work there. Do you see the same behavior?
I see nothing in the terminal, and in my other application only the last line is displayed. I can place breakpoints, see variables... before I have to send keys to ncurses. The application works, it is just all ncurses related things that do not.
looks like a problem with tty... Can you try to run the application and then attach to it with the debugger, it should work fine after that. You can use easy attach button in the output tab (under stop/rerun buttons)
Works fine with debugger attach, but not so friendly than directly clicking on the debugger button :) Thanks for this workaround, can now works far faster, but if you can found a fix for Netbeans 6.9 would be perfect
I will try to fix it somehow, unfortunately gdb from the console works the same way (when you use separate tty).
*** Bug 178159 has been marked as a duplicate of this bug. ***