target sim, where does output go?

[xyxxx]

We intend to use arm-eabi-gcc under Windows. We seem to have installed, and can at least compile a simple hello world program. However, we are unclear how to see the output. We've run arm-eabi-gdb a.out, done a 'target sim' and then a run, however, (1) there is never anything output and (2) the application never seems to terminate. Looking at say http://www.drrtos.org/downloads/GettingStarted.pdf implies it is at least possible with other gnu based arm compilers and affiliated gdb's. Do we need to arm-eabi-gcc with a certain option under this gcc variant? TIA.

[xyxxx]

Are we the only ones not getting stdout/stderr output from target sim?

[WinterMute]

I'll have a look at this soon, this is because devkitARM is built with --disable-newlib-supplied-syscalls and uses a pseudo device API to connect up output & storage devices. The current default stdio hooks in libsysbase are null devices so I might take a look at using a different default libgloss layer which falls back to the old code used for newlib supplied syscalls. Apologies for the confusion.

[xyxxx]

Ok, thanks. We have since downloaded Sourcery for ARM's gcc, and it exhibited the same problem until we figure out have to specify a -T option for a "basic" linker script that target sim liked. We will play around with this and devkitARM this week and see if it helps, although if we understand you, the output we're trying to establish is dummied out, so we won't break out neck trying to do it beyond a quick try

BTW, don't have the install in front of me, but there is some sort of libsim.a (not the exact name) high'ish up in the install tree somewhere. What is that for?

[xyxxx]

Any progress in resolving this? TIA.

[xyxxx]

Any feedback on this would be appreciated, thanks.