From ffdc2c5396903ec0dd2b7ab4623f7f7674827885 Mon Sep 17 00:00:00 2001 From: Allan McRae Date: Sat, 8 Mar 2014 16:58:30 +1000 Subject: Use MALLOC throughtout libalpm Use MALLOC instead of malloc for safety in libalpm. Some changes are pure refactoring, but for others this provides a success check for memory allocation. Signed-off-by: Allan McRae --- lib/libalpm/be_local.c | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) (limited to 'lib/libalpm/be_local.c') diff --git a/lib/libalpm/be_local.c b/lib/libalpm/be_local.c index 5474995e..9a9bdef6 100644 --- a/lib/libalpm/be_local.c +++ b/lib/libalpm/be_local.c @@ -743,11 +743,7 @@ static int local_db_read(alpm_pkg_t *info, alpm_dbinfrq_t inforeq) /* since we know the length of the file string already, * we can do malloc + memcpy rather than strdup */ len += 1; - files[files_count].name = malloc(len); - if(files[files_count].name == NULL) { - _alpm_alloc_fail(len); - goto error; - } + MALLOC(files[files_count].name, len, goto error); memcpy(files[files_count].name, line, len); files_count++; } -- cgit v1.2.3-24-g4f1b