database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-07-09 22:41:56 +03:00
Code Activity

Fix pg_dump crashes caused by bogus use of va_start/va_end (only seen

Browse Source 
on some platforms, which is not too surprising considering how platform
specific these macros must be).
This commit is contained in:
Tom Lane
2001-02-23 22:52:32 +00:00
parent b25e60d887
commit 2b0f8ae009
2 changed files with 20 additions and 22 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
src/bin/pg_dump/pg_backup_tar.c
View File

@ -899,24 +899,22 @@ static int tarPrintf(ArchiveHandle *AH, TAR_MEMBER *th, const char *fmt, ...)
int bSize = strlen(fmt) + 256; /* Should be enough */
int cnt = -1;
va_start(ap, fmt);
/* This is paranoid: deal with the possibility that vsnprintf is willing to ignore trailing null */
/* or returns > 0 even if string does not fit. It may be the case that it returns cnt = bufsize */
while (cnt < 0 || cnt >= (bSize - 1) ) {
while (cnt < 0 || cnt >= (bSize - 1) )
{
if (p != NULL) free(p);
bSize *= 2;
p = (char*)malloc(bSize);
if (p == NULL)
{
va_end(ap);
die_horribly(AH, "%s: could not allocate buffer for ahprintf\n", progname);
die_horribly(AH, "%s: could not allocate buffer for tarPrintf\n", progname);
}
va_start(ap, fmt);
cnt = vsnprintf(p, bSize, fmt, ap);
va_end(ap);
}
va_end(ap);
cnt = tarWrite(p, cnt, th);
free(p);
return cnt;
}