On Tue, 26 Jan 2010, Spencer Oliver wrote: > David Brownell wrote: > > On Tuesday 26 January 2010, Spencer Oliver wrote: > >> I could not get the original implementation from Nicolas Pitr working > >> when outputting to stdout. > > > > For the record: I did get that working with an ARM9, no > > changes, using the latest CodeSourcery EABI toolchain. > > > > strange, i tested on arm9 aswell. > fileio was ok, just printf to stdout/stderr failed.
It is used in production settings here, so if it didn't work on ARM9 I would have fixed it long ago. ;-) > > The only moderately surprising behavior was seeing the > > output mixed with server logging stuff, without any > > particular fanfare ... I had expected to see it with > > the telnet console I was using at the time. (Didn't > > try it with GDB.) I went for the easiest setup. Typically this is used with applications on the target that don't need debugging but only a communication channel. Here openocd is fired up with a script that loads the application on the target and the application starts talking to you right away on the same console without having to telnet anywhere (works fine with pipes and redirects, such as through interaction with a chat script). Of course when the remote application calls out to gets() when asking user input then openocd is completely stalled by the synchronous read() on the local stdin, which means this doesn't interact well with gdb nor the telnet session in that case of course. The "fix" might require quite significant rearchitecturing of openocd. Nicolas _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
