Displaying 20 results from an estimated 2335 matches for "snprintfs".
Did you mean:
snprintf
2000 Jan 12
4
solaris 2.5.1 still no good
Hello,
I've got the same problem like this one.
Can somebody send the snprintf.c or other ways around please?
Thanks,
<------- snipped from mail archive ---------------------------------->
I just email'd, from my other account, the snprintf.c that we distribute
in PostgreSQL...its been thoroughly tested on all the platforms that we
support, with Solaris 2.5.1 being one of
1999 Dec 09
1
solaris 2.5.1 still no good
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi folks,
Here's what I get under solaris 2.5.1 (sparc) with gcc-2.95.2 and
gnumake 3.78-something :
bsd-snprintf.c: In function `msetup':
bsd-snprintf.c:67: warning: implicit declaration of function
`getpagesize'
bsd-snprintf.c:72: `x' undeclared (first use in this function)
bsd-snprintf.c:72: (Each undeclared identifier is reported
2009 Apr 30
0
[LLVMdev] Stack alignment in JIT compiled code
Hello, Simon
> So far, i found no way to denote calls to the host function as aligned
> or maintain stack alignment throughout the stack frame of the jit
> compiled function. Further, the gcc front end (llvm-g++ (GCC) 4.2.1)
> seems to ignore directives such as -mpreferred-stack-boundary.
Mike is right. It depends on your subtarget:
1. If you're running stuff on Darwin, which has
2025 Apr 11
8
[Bug 3809] New: snprintf const char *fmt detection false negatives with Clang and _FORTIFY_SOURCE=2
https://bugzilla.mindrot.org/show_bug.cgi?id=3809
Bug ID: 3809
Summary: snprintf const char *fmt detection false negatives
with Clang and _FORTIFY_SOURCE=2
Product: Portable OpenSSH
Version: -current
Hardware: amd64
OS: FreeBSD
Status: NEW
Severity: enhancement
Priority: P5
2009 May 01
3
[LLVMdev] Stack alignment in JIT compiled code
On Linux x86_64, it is different. The x86-64 ABI says
(http://www.x86-64.org/viewvc/trunk/x86-64-ABI/low-level-sys-info.tex?revision=84&content-type=text%2Fplain):
>>
The end of the input argument area shall be aligned on a 16 byte boundary.
In other words, the value (%rsp - 8) is always a multiple of 16 when control is
transferred to the function entry point. The stack pointer, %rsp,
2009 Apr 30
3
[LLVMdev] Stack alignment in JIT compiled code
Hi all,
i am trying to call an aligned function in my host application from jit
compiled bitcode. The call itself is done using an absolute pointer to
the function. The host application's functions make heavy use of SSE
instructions and are thus operate on a stack aligned to 16 byte.
If i call an aligned function in the host application from a frame
running jit compiled code, the alignment
2015 Feb 11
3
Samba 4.2.0rc4 fails to start up
> On Wed, Feb 11, 2015 at 11:13:42AM +0100, Volker Lendecke wrote:
> > On Tue, Feb 10, 2015 at 08:59:21PM -0800, Jeremy Allison wrote:
> > > Ah ok - I expected as much. snprintf seems to be
> > > broken in that it's returning -1.
> > >
> > > Is this our snprintf or one from Solaris ? Can
> > > you try and track down why it's returning
1997 Jul 08
3
so-called snprintf() in db-1.85.4
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
2010 Oct 25
1
[LLVMdev] sprintf -> snprintf conversion
Hello, llvmdev!
I'm using LLVM on OpenBSD. This project proactively advocates usage
of 'secure' C apis, especially related to memory bounds checking.
Thus using functions like sprintf/strcpy/etc usually spits out a
linker warning in base toolchain like this one:
/home/proger/dev/llvm/Debug+Asserts/lib/libclangFrontend.a(DocumentXML.o) (.text+0xc65): In function
2001 Oct 18
2
Incorrect return types for snprintf() and vsnprintf()
Both 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,
2000 Feb 21
1
OpenSSH doesn't compile under Solaris 2.3 Sparc
Hi,
We are trying to get OpenSSH-1.2.2 stable release to compile under Solaris
2.3 Sparc. It worked perfect for Solaris 2.5, Solaris 2.5.1, Solaris 7 (All
on Sparc) and Linux 2.2.13 Intel x86
OpenSSL installs fine without problem, zlib is installed fine without
problems and egd.pl installs fine without problems. These are all the
current releases, I can get the version numbers if you need
2003 Apr 08
1
compile 11.00 parisc1.1 32-bit fails - snprintf
I am having trouble compiling rsync 2.5.6 for HPUX 11.00.
The system I am using has a number of patches, although I admit not having
verified that it is completely up to date.
I have found gcc 3.2 and gmake and installed them.
- configure seems to work fine. (my use ./configure
--prefix=/opt/trial/local --with-rsync-path=/opt/trial/local/bin/rsync)
- it finds snprintf and vsnprintf but not C99
2011 Jul 05
6
[PATCH 1/7] ln: Check snprintf() return values
Add some semi-useful error message, as printing the failing dir or file
seems not really advisable after that error.
Signed-off-by: maximilian attems <max at stro.at>
---
usr/utils/ln.c | 20 +++++++++++++++-----
1 files changed, 15 insertions(+), 5 deletions(-)
diff --git a/usr/utils/ln.c b/usr/utils/ln.c
index e826eb8..257b33f 100644
--- a/usr/utils/ln.c
+++ b/usr/utils/ln.c
@@ -9,7
2001 Feb 12
5
SCO OS3 build broken (CVS 01/12/01)
It looks like something got broken in openbsd-compat/bsd-snprintf.c
...
gcc -g -O2 -Wall -Dftruncate=chsize -I/usr/local/include -I/usr/local/ssl/includ
e -I. -I.. -I../src/openbsd-compat -I../src/openbsd-compat/.. -DHAVE_CONFIG_H -c
../src/openbsd-compat/bsd-snprintf.c
In file included from ../src/openbsd-compat/bsd-snprintf.c:72:
2013 Mar 15
2
snprintf and MS Visual Studio
Christoph Terasa wrote:
> Since MS refuses to support C99, the common practice is to use either
>
> sprintf_s:
> http://msdn.microsoft.com/en-us/library/ce3zzk1k(v=VS.80).aspx
> _snprintf_s:
> http://msdn.microsoft.com/de-de/library/f30dzcf6(v=VS.80).aspx
>
> The former can be used as a drop-in replacement of snprintf via a
> define, the latter takes an
2024 May 23
4
[PATCH 0/4] drm: enable -Wformat-truncation
Jani Nikula (4):
drm/amdgpu: fix -Wformat-truncation warning in
amdgpu_gfx_kiq_init_ring()
drm/nouveau: fix -Wformat-truncation warning in
nouveau_backlight_init()
drm/imx: fix -Wformat-truncation warning in imx_ldb_probe()
drm: enable -Wformat-truncation across the subsystem
drivers/gpu/drm/Makefile | 3 +--
drivers/gpu/drm/amd/amdgpu/amdgpu_gfx.c | 6
2010 Mar 05
2
[PATCH] R ignores PATH_MAX and fails in long directories (PR#14228)
Full_Name: Murray Stokely
Version: 2.10.1
OS: Linux
Submission from: (NULL) (216.239.45.4)
The Defn.h header includes limits.h for PATH_MAX and then checks if it hasn't
been defined and if not sets something manually. Some of the R code uses
PATH_MAX but a lot of other functions in unix/sys-unix.c and main/startup.c just
hardcodes a limit of 256 characters.
In my environment this is not
2015 Feb 11
4
Samba 4.2.0rc4 fails to start up
I added debuging as follows:
/* no O_EXCL, existence check is via the fcntl lock */
lockfile_fd = open(lockfile_name.buf, O_NONBLOCK|O_CREAT|O_WRONLY,
0644);
if (lockfile_fd == -1) {
ret = errno;
DEBUG(1, ("%s: open failed: %s\n", __func__, strerror(errno)));
return ret;
}
2020 Apr 30
1
Translations and snprintf on Windows
[a bit unsure on if this is maybe better for r-package-devel]
We recently added translations to messages at the R and C level to
data.table.
At the C level, we did _() wrapping for char arrays supplied to the
following functions: error, warning, Rprintf, Error, and snprintf.
This seemed OK but the use of snprintf specifically appears to have caused
a crash on Windows:
2004 Apr 30
1
problem conpiling snprintf.c
>From Michele Cawley
problem: tring to install on a HPUX v11 system. make install comming back
with below error.
Using LIBS = -lgen -lsec -lnsl
Compiling lib/snprintf.c
lib/snprintf.c:792: conflicting types for `snprintf'
/usr/local/lib/gcc-lib/hppa2.0n-hp-hpux11.00/3.1/include/stdio.h:493:
previous d
eclaration of `snprintf'
*** Error exit code 1
Stop.
regards
Michele