On Tuesday 08 November 2011 16:44:19 Bob Smith wrote:
> On 11/4/2011 8:01 PM, Marc wrote:
> > On Nov 5, 12:23 am, Bob Smith wrote:
> >> Using MPIR 2.4.0, I'm substituting my own memory allocator which gets
> >> called from tal-reent.c in __gmp_tmp_reentrant_alloc. The code in that
> >> function d
On Nov 8, 5:44 pm, Bob Smith wrote:
> On 11/4/2011 8:01 PM, Marc wrote:
>
> > On Nov 5, 12:23 am, Bob Smith wrote:
> >> Using MPIR 2.4.0, I'm substituting my own memory allocator which gets
> >> called from tal-reent.c in __gmp_tmp_reentrant_alloc. The code in that
> >> function doesn't check to
On 11/4/2011 8:01 PM, Marc wrote:
On Nov 5, 12:23 am, Bob Smith wrote:
Using MPIR 2.4.0, I'm substituting my own memory allocator which gets
called from tal-reent.c in __gmp_tmp_reentrant_alloc. The code in that
function doesn't check to see if the allocation failed and immediately
writes into
On Nov 5, 12:23 am, Bob Smith wrote:
> Using MPIR 2.4.0, I'm substituting my own memory allocator which gets
> called from tal-reent.c in __gmp_tmp_reentrant_alloc. The code in that
> function doesn't check to see if the allocation failed and immediately
> writes into the memory, allocated or not
