Re: printf(3): extra parameters, %b token, and cpp antics

2017-04-23 Thread Otto Moerbeek
On Sun, Apr 23, 2017 at 06:01:18PM +1000, Damian McGuckin wrote: > On Sun, 23 Apr 2017, Jonathan Gray wrote: > > > http://man.openbsd.org/printf.9 > > Is the use of '%b' an addressing-out-of-bounds bug waiting to happen or is > there some sort of inbuilt protection that I cannot see? > > Regard

Re: printf(3): extra parameters, %b token, and cpp antics

2017-04-23 Thread Damian McGuckin
On Sun, 23 Apr 2017, Jonathan Gray wrote: http://man.openbsd.org/printf.9 Is the use of '%b' an addressing-out-of-bounds bug waiting to happen or is there some sort of inbuilt protection that I cannot see? Regards - Damian Pacific Engineering Systems International, 277-279 Broadway, Glebe

Re: printf(3): extra parameters, %b token, and cpp antics

2017-04-23 Thread Jonathan Gray
On Sun, Apr 23, 2017 at 03:39:22AM -0400, Ian Sutton wrote: > I noticed some strange code in src/sys/arch/armv7/omap/ommmc.c > > This preprocessor define seems to map intr. state bit positions with > strings describing them: > > 149 #define MMCHS_STAT_FMT "\20" \ > 150 "\x09d_BADA" \ > 151

Re: printf(3): extra parameters, %b token, and cpp antics

2017-04-23 Thread Sebastien Marie
On Sun, Apr 23, 2017 at 03:39:22AM -0400, Ian Sutton wrote: > > So through some combination of: > * CPP multi-string define with unclear hex escapes prepended > * printf() call with one too many parameters > * undocumented %b printf() token you didn't look at the right printf ma

printf(3): extra parameters, %b token, and cpp antics

2017-04-23 Thread Ian Sutton
I noticed some strange code in src/sys/arch/armv7/omap/ommmc.c This preprocessor define seems to map intr. state bit positions with strings describing them: 149 #define MMCHS_STAT_FMT "\20" \ 150 "\x09d_BADA" \ 151 "\x09c_CERR" \ 152 "\x098_ACE" \ 153 "\x096_DEB" \ 154 "\x095