Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: James Almer <jamrial@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] av_mallocz_array
Date: Wed, 15 Mar 2023 18:41:43 -0300
Message-ID: <960bbb76-4a47-b030-01e5-c588907f1a31@gmail.com> (raw)
In-Reply-To: <903dc782-d0e5-2169-b5f2-75337fafedbc@numericable.fr>

On 3/15/2023 6:40 PM, Christophe GARNIER wrote:
> Hello,
> 
> To build makemkv version 1.17.3 (makemkv-oss), I retreived he sources of 
> ffmpeg from the git repository (git clone 
> https://git.ffmpeg.org/ffmpeg.git ffmpeg).It appeared that the function 
> av_mallocz_array is not present into libavutil/mem.c and libavutil/mem.h.
> 
> I had the following code into libavutil/mem.c :
> 
> void *av_mallocz_array(size_t nmemb, size_t size)
> {
>     size_t result;
>     if (size_mult(nmemb, size, &result) < 0)
>         return NULL;
>     return av_mallocz(result);
> }
> 
> and into libavutil/mem.h :
> 
> /**
> * Allocate a memory block for an array with av_mallocz().
> *
> * The allocated memory will have size `size * nmemb` bytes.
> *
> * @param nmemb Number of elements
> * @param size  Size of the single element
> * @return Pointer to the allocated block, or `NULL` if the block cannot
> *         be allocated
> *
> * @see av_mallocz()
> * @see av_malloc_array()
> */
> av_alloc_size(1, 2) void *av_mallocz_array(size_t nmemb, size_t size);
> 
> After these modifications, I have been able to generate makemkv-oss.

Use av_calloc() instead.
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".

  reply	other threads:[~2023-03-15 21:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-15 21:40 Christophe GARNIER
2023-03-15 21:41 ` James Almer [this message]
2023-05-04  9:06 Christophe GARNIER
2023-05-04  9:18 ` Paul B Mahol
2023-05-04 10:13 ` Hendrik Leppkes

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=960bbb76-4a47-b030-01e5-c588907f1a31@gmail.com \
    --to=jamrial@gmail.com \
    --cc=ffmpeg-devel@ffmpeg.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
		ffmpegdev@gitmailbox.com
	public-inbox-index ffmpegdev

Example config snippet for mirrors.


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git