From mboxrd@z Thu Jan 1 00:00:00 1970 From: Braxton Thomason To: Keith Seitz Cc: insight@sourceware.cygnus.com Subject: Re: GDB Console Q Date: Thu, 02 Mar 2000 09:15:00 -0000 Message-id: References: <38BE9F62.900E0494@firetalk.com> X-SW-Source: 2000-q1/msg00103.html Actually, that was not quite the problem. I didnt make myself clear, sorry. :) The _real_ problem is this: (gdb) n 6: currentStage->mName.mName.dat = 0x20004398 "Execute" (gdb) and so on is the "normal" behavior, and I get the output on my xterm. Thats fine. The problem arises sometimes when I press run in the GUI, I get this behavior from my GDB console: (gdd) n (gdb) print foo (gdb) info breakpoints (gdb) info display (gdb) display foo (gdb) //ARG!!!!! NOThING!! ? thanks, brax. On Thu, 2 Mar 2000, Keith Seitz wrote: > Braxton Thomason wrote: > > > > Has anyone had problems with the GDB console in Insight not displaying > > anything after pressing the "Run" button in the GUI? I am runing on AIX > > 4.3.2.. > > > > Wondering if I should follow it up, or forget it... > > Ugh. This is a sad state of affairs... All console I/O for native > targets goes to the controlling xterminal where insight was launched. It > does NOT go to the console window. I had some code from Tom Tromey > (tromey@cygnus.com) that demonstrated how gdbtk/Insight could open a new > xterm for the child process, but I never got around to implementing it. > I kinda like the current behavior. (Whether that's because I really do > like it or because I am just used to it doing that is a mystery to me. > :-) > > So, rest assured: what you are observing is "normal". (Now, if you don't > see your programs output in the xterm, that's another problem > altogether.) > > Keith > -- > Why chat when you can Firetalk? > Firetalk ID: Keith (10320) > www.firetalk.com >