[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#13098: [PATCH] cut.c: Fix memory leak
From: |
Cojocaru Alexandru |
Subject: |
bug#13098: [PATCH] cut.c: Fix memory leak |
Date: |
Thu, 6 Dec 2012 17:59:41 +0100 |
> Hmm, it might be a bit more consistent to guard all
> references to the bit vector array with max_range_endpoint?
> How about the attached?
I checked for `n_rp' and `printable_field' becuase it felt more
natural.
I reasoned as follows: first check if we have any finite ranges (n_rp) if yes,
allocate memory for `printable_field'. Then check if `printable_field'
has been allocated memory, if yes access it.
Anyway both are good solutions.
Best regards,
Cojocaru Alexandru