# \#stdio

**URL:** https://forums.digi.com/tag/stdio/651.md

[Latest](https://forums.digi.com/latest.md) · [Categories](https://forums.digi.com/categories.md) · [Tags](https://forums.digi.com/tags.md)

---

## [STDIO.LIB library bug report, "\_atodt" giving strange results](https://forums.digi.com/t/stdio-lib-library-bug-report-atodt-giving-strange-results/11763)

<div class="topic-metadata">

**Author:** [@tito.brasolin](https://forums.digi.com/u/tito.brasolin)\
**Replies:** 4\
**Last updated:** [August 14, 2013, 9:24am UTC](https://forums.digi.com/t/stdio-lib-library-bug-report-atodt-giving-strange-results/11763 "2013-08-14T09:24:50Z")

</div>

The aforementioned function \_atodt doesn’t seem to work well (DC 10.70 and 72) sometimes it returns partially random results. In my opinion, it’s because the “t” structure is not initialized. Line 2328: auto struct tm…

---

## [How do I redirect STDIO to the DIAG header?](https://forums.digi.com/t/how-do-i-redirect-stdio-to-the-diag-header/11819)

<div class="topic-metadata">

**Author:** [@jonmartin111](https://forums.digi.com/u/jonmartin111)\
**Replies:** 1\
**Last updated:** [August 6, 2013, 11:34am UTC](https://forums.digi.com/t/how-do-i-redirect-stdio-to-the-diag-header/11819 "2013-08-06T11:34:50Z")

</div>

RCM4000. I’d like to be able to see the STDIO output when the device is not in debug mode using the DIAG header.
