From mboxrd@z Thu Jan 1 00:00:00 1970 From: bgat@open-widgets.com To: Jonathan Larmour Cc: ecos-discuss@sources.redhat.com Subject: Re: [ECOS] Turn off gdb console? Date: Wed, 31 Jan 2001 13:19:00 -0000 Message-id: <20010131151911.A14768@sr1.open-widgets.com> References: <20010130164509.B13358@sr1.open-widgets.com> <3A77816B.EE5B07F1@redhat.com> X-SW-Source: 2001-01/msg00505.html Jifl: That's EXACTLY what I was looking for, for now. Thanks! b.g. On Wed, Jan 31, 2001 at 03:07:23AM +0000, Jonathan Larmour wrote: > bgat@open-widgets.com wrote: > > > > Hi! Quick question... > > > > I'm trying to run the test applications in the latest eCos CVS > > repository, like dhrystone, over ethernet using RedBoot on the MBX. > > As expected, whenever there's a printf() in dhrystone, it shows up on > > the serial port, formatted as a gdb "console output" message. > > > > This behavior would make sense if I was talking to the MBX target over > > the serial port, but I'm not. Furthermore, what I would like to see > > is raw, streaming output from dhrystone on the serial port; I want to > > control the application via ethernet, but not have the console tied to > > gdb's console. > > > > I gave my ecos.ecc file a quick skim, and didn't come across anything > > that was obviously related to console output formatting. What's the > > CYG_xxx that I use? > > Believe it or not, we're just working on a generic solution to this type of > situation that will allow a loaded application to claim the > console/debugging virtual vectors > > But for now I believe you should be able to enable the option > CYGDBG_HAL_DIAG_DISABLE_GDB_PROTOCOL, which should turn off GDB packet > encoding in the MBX hal diag output (assuming you have not explicitly > enabled virtual vector diag). > > Jifl > -- > Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062 > Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine > -- Bill Gatliff bgat@open-widgets.com