On 9/17/2013 9:16 AM, Sebastian Huber wrote:
On 2013-09-17 16:05, Joel Sherrill wrote:
Hi
Take a peek at Issue 1063872 and 1063873. These are in main_help.c
and I think Scan is not happy with newlib's putchar() macro. It
increments the buffer pointer but it always ends up one past
what you use
Hi
Take a peek at Issue 1063872 and 1063873. These are in main_help.c
and I think Scan is not happy with newlib's putchar() macro. It
increments the buffer pointer but it always ends up one past
what you use on any given call.
Since the pointer ends up pointing at something which is not
visibly
On 2013-09-17 16:05, Joel Sherrill wrote:
Hi
Take a peek at Issue 1063872 and 1063873. These are in main_help.c
and I think Scan is not happy with newlib's putchar() macro. It
increments the buffer pointer but it always ends up one past
what you use on any given call.
Since the pointer ends up