Is Watcom's snprintf broken?

I’ve recently ported two packages (shadow, wu-ftpd) to QNX. I got past the
configuration and porting problems but couldn’t get them to run until I
recompliled them using the snprintf.c included in shadow’s lib directory.
The one in clib3r kept causing segment violations. Everything appears to be
working fine now. Is this a general problem or just something broken on my
system?

“Roger Swift” <roger.o.swift@exxonmobil.com> wrote in message
news:afaalp$fhf$1@inn.qnx.com

I’ve recently ported two packages (shadow, wu-ftpd) to QNX. I got past the
configuration and porting problems but couldn’t get them to run until I
recompliled them using the snprintf.c included in shadow’s lib directory.
The one in clib3r kept causing segment violations. Everything appears to
be
working fine now. Is this a general problem or just something broken on my
system?

#define snpribtf _bprintf” inside stdio. :slight_smile: works fine for me without any
SIGSEGVs.

// wbr