search for: vsnprintf

lvqcl wrote: > I wrote a small program that fills a buffer[] with "abcdefghijklmnopqrstuvwxyz\0" > pattern and then tries to write "0123456789" string into it. > It calls either > ret = vsnprintf_s(buffer, buf_size, _TRUNCATE, fmt, va); > or > ret = vsnprintf(buffer, buf_size, fmt, va); <snip> > vsnprintf (MSVC, MinGW): > > buf_size = 8; ret = -1; buffer = "01234567ijklmnopqrstuvwxyz" > buf_size = 9; ret = -1; buffer =...

Erik de Castro Lopo wrote: >> vsnprintf (MSVC, MinGW): >> >> buf_size = 8; ret = -1; buffer = "01234567ijklmnopqrstuvwxyz" >> buf_size = 9; ret = -1; buffer = "012345678jklmnopqrstuvwxyz" >> buf_size = 10; ret = 10; buffer = "0123456789klmnopq...

Could Rvsnprintf (in src/main/errors.c) be added to the R API with prototype in include/R_ext/Print.h say? Here's my problem. I'm trying to write some code that is not totally tied to R. Hence I want R style error messaging to be isolated in a small module. I do not want #include <R.h> and calls t...

I think I stumbled upon a bug in the i_snprintf() function. In the case of vnsprintf() being available, it depends on vnsprintf() returning -1 when the string was longer than the passed-in limit (or it won't terminate the string.). But this isn't the C99-standardized behaviour, and newer glibc's don't do that anymore either, so you can end up with a non-terminated string. This

...from usr/klibc/inet/inet_ntoa.c:6: linux/include/linux/in.h:182: error: expected specifier-qualifier-list before 'sa_family_t' make[2]: *** [usr/klibc/inet/inet_ntoa.o] Error 1 make[1]: *** [all] Error 2 make: *** [klibc] Error 2 [4] build log on x86: KLIBCCC usr/klibc/vsnprintf.o In file included from usr/include/arch/i386/klibc/archsignal.h:99, from usr/klibc/../include/signal.h:14, from usr/klibc/../include/sys/select.h:11, from usr/klibc/../include/unistd.h:12, from usr/klibc/../include/stdio.h:11,...

...oth of these functions are using strlen() to create return value. Cheers, Scott Rankin *** /openbsd-compat/bsd-snprintf.c.orig Thu Oct 18 13:57:51 2001 --- /openbsd-compat/bsd-snprintf.c Thu Oct 18 13:58:26 2001 *************** *** 632,638 **** #endif /* !defined(HAVE_SNPRINTF) || !defined(HAVE_VSNPRINTF) */ #ifndef HAVE_VSNPRINTF ! int vsnprintf(char *str, size_t count, const char *fmt, va_list args) { str[0] = 0; --- 632,638 ---- #endif /* !defined(HAVE_SNPRINTF) || !defined(HAVE_VSNPRINTF) */ #ifndef HAVE_VSNPRINTF ! size_t vsnprintf(char *str, size_t count, const char *fmt, va_...

lvqcl wrote: > Why? We can use vsnprintf_s for MSVS, and vsnprintf for MinGW. > > MSVS version of vsnprintf_s is located inside (statically linked) msvcp???.lib > or (dynamically linked) msvcp???.dll. They are part of MSVS runtime, and compatible > with WinXP. So it is safe to use it in FLAC. Oh, ok. I missed this bit. I know...

http://bugzilla.mindrot.org/show_bug.cgi?id=1133 Summary: configure.ac sets wrong BROKEN_ var (snprintf/vsnprintf) Product: Portable OpenSSH Version: -current Platform: HPPA OS/Version: HP-UX Status: NEW Severity: major Priority: P2 Component: Build system AssignedTo: bitbucket at mindrot.org ReportedBy: dleonard a...

Erik de Castro Lopo wrote: >> Oops. It seems that vsnprintf_s isn't always available on MinGW platform: >> MinGW declares this function only if MINGW_HAS_SECURE_API macro is defined. >> That's because WinXP version of msvcrt.dll doesn't contain secure functions >> like vsnprintf_s. >> >> Maybe it's better to rev...

Hi All, I tried to build dovecot-1.1.rc9 on a HP-UX machine, but failed to configure with the following message: configure: error: You don't appear to have C99 compatible vsnprintf() call The environment is like the following: - command: ./configure - uname: HP-UX B.11.23 U ia64 - aCC version: HP aC++/ANSI C B3910B A.05.55 [Dec 04 2003] Also, I tried to run `./configure CC=c99' and `./configure CC="/opt/aCC/bin/aCC -Ae" also, but the result was the same....

Fix an off-by-one in asprintf and vasprintf. The return of vsnprintf is the number of bytes *not* including the terminating '\0'. The size argument to vsnprintf is the number of bytes *including* the terminating '\0'. diff -u klibc-0.188/klibc/asprintf.c udev/klibc-0.188/klibc/asprintf.c --- klibc-0.188/klibc/asprintf.c 2004-10-22 12:07:22.6...

...|Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID ------- Additional Comments From Darren.Moffat at Sun.COM 2001-12-12 06:06 ------- The vsnprintf is a red herring, note that the error message comes from ld.so.1 when loading the acomp program. What this is saying is that acomp actually calls vsnprintf but ld.so.1 couldn't resolve that symbol. Since the Forte Developer 6 update 1 acomp was compiled and linked on Solaris 2.6, it won't...

The snprintftest.c regression test in openbsd-compat/regress has a buffer overflow error, and an argument error in the calls to snprintf(), and vsnprintf(). On line 49 of snprintftest.c, the character buffer, b, is allocated at 5 bytes. However, in the calls to snprintf and vsnprintf, on lines 68 and 77 respectively, it is expected to place 11 bytes of data into the buffer. Which will result in buffer overflow. The second error is in the ar...

If the linux kernel was built using O=builddir, there is no correct choice for the linux symlink in klibc-1.5. See below for the possible outcomes: ----------------------- KLIBCCC usr/klibc/vsnprintf.o In file included from usr/include/sys/types.h:15, from usr/include/unistd.h:11, from usr/include/stdio.h:11, from usr/klibc/vsnprintf.c:13: linux/include/linux/posix_types.h:47:29: asm/posix_types.h: No such file or directory In file included fr...

Hi, There is a severe problem with the db-1.85.4 library''s Linux port that can be found on sunsite.unc.edu under /pub/Linux/libs/db-1.85.4-src.tar.gz (sp?): This library contains a "snprintf" function which breaks down to a common sprintf, ignoring the size parameter. Obviously, this was thought to be a terribly bad work-around for C libraries which don''t contain an

lvqcl wrote: > Oops. It seems that vsnprintf_s isn't always available on MinGW platform: > MinGW declares this function only if MINGW_HAS_SECURE_API macro is defined. > That's because WinXP version of msvcrt.dll doesn't contain secure functions > like vsnprintf_s. > > Maybe it's better to revert vsnprintf_s to...

...\ - strncasecmp.o strncat.o strncmp.o strncpy.o strndup.o \ + strncasecmp.o strncat.o strncmp.o strncpy.o strndup.o strnlen.o \ strntoimax.o strntoumax.o strrchr.o strsep.o strspn.o strstr.o \ strtoimax.o strtok.o strtol.o strtoll.o strtoul.o strtoull.o \ strtoumax.o vfprintf.o vprintf.o vsnprintf.o vsprintf.o \ --- syslinux-3.36/com32/lib/vsnprintf.c.orig 2007-02-10 21:47:08.000000000 +0100 +++ syslinux-3.36/com32/lib/vsnprintf.c 2007-04-12 12:08:54.000000000 +0200 @@ -362,7 +362,7 @@ case 's': /* String */ sarg = va_arg(ap, const char *); sarg = sarg ? sarg : "...

Erik de Castro Lopo wrote: >> MSVS version of vsnprintf_s is located inside (statically linked) msvcp???.lib >> or (dynamically linked) msvcp???.dll. They are part of MSVS runtime, and compatible >> with WinXP. So it is safe to use it in FLAC. > > Oh, ok. I missed this bit. I know so very little about Windows. > > However, if you...

I'm wonder if anyone happens to have a simplier (slower) version of bsd-snprintf.c. It seems NeXT 3.3 (unsure about 4.2) is missing mprotect(). If I could get something to replace that for a while and fix some of theses utmp in login.c issues I may have a rough port NeXT to black hardware.=) Thanks

...ht I would try klibc since I could then base my port more closely on the Ubuntu/Debian work. Problem is I can't seem to get klibc to build against the RHEL 4 kernel (2.6.9 with a boatload of patches). Here is the result of the make command: [root@****** klibc-1.5.4]# make KLIBCCC usr/klibc/vsnprintf.o In file included from linux/include/linux/linkage.h:4, from linux/include/asm-generic/signal.h:5, from usr/include/arch/i386/klibc/archsignal.h:99, from usr/klibc/../include/signal.h:14, from usr/klibc/../include/sys/select.h:11,...