You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello.
I'm from Russia, and i'm sorry for my bad English.
I want to use Sublime2 like IDE for C++ developing, and I need the debug my programs with SublimeGDB.
So I have a one question: if my program have reading data from stdin, how and where I can input it for program? And where the output for stdout is printed?
When I use GDB from my console, the program make pause and wait input from GDB-console. Output also printed to GDB-console. I don't see it in SublimeGDB.
How to fix it? It is possible?
So, a have this message on "GDB console" tab while debugging: "warning: GDB: Failed to set controlling terminal: \320\235\320\265\320\277\321\200\320\270\320\274\320\265\320\275\320\270\320\274\321\213\320\271 \320\272 \320\264\320\260\320\275\320\275\320\276\320\274\321\203 \321\203\321\201\321\202\321\200\320\276\320\271\321\201\321\202\320\262\321\203 ioctl\n".
The text was updated successfully, but these errors were encountered:
Hello.
I'm from Russia, and i'm sorry for my bad English.
I want to use Sublime2 like IDE for C++ developing, and I need the debug my programs with SublimeGDB.
So I have a one question: if my program have reading data from stdin, how and where I can input it for program? And where the output for stdout is printed?
When I use GDB from my console, the program make pause and wait input from GDB-console. Output also printed to GDB-console. I don't see it in SublimeGDB.
How to fix it? It is possible?
So, a have this message on "GDB console" tab while debugging: "warning: GDB: Failed to set controlling terminal: \320\235\320\265\320\277\321\200\320\270\320\274\320\265\320\275\320\270\320\274\321\213\320\271 \320\272 \320\264\320\260\320\275\320\275\320\276\320\274\321\203 \321\203\321\201\321\202\321\200\320\276\320\271\321\201\321\202\320\262\321\203 ioctl\n".
The text was updated successfully, but these errors were encountered: