On Mon, 18 Nov 2002 13:31:58 +0100, Marcus Börger wrote:
>At 13:07 18.11.2002, Derick Rethans wrote:
>>On Mon, 18 Nov 2002, Brian Havard wrote:
>>
>> > Derick Rethans wrote:
>> > > On Sun, 17 Nov 2002, Derick Rethans wrote:
>> > >
>> > >
>> > >>On Sun, 17 Nov 2002, Brian Havard wrote:
>> > >>
>> >
On November 18, 2002 07:44 am, Derick Rethans wrote:
> On Mon, 18 Nov 2002, Marcus Börger wrote:
> > Brian could you create a short test for the segfault? It would help us
> > finding out the problems.
>
> For now I think it's very wise to remove all the e*() memory functions
> from the branch, it'
On Mon, 18 Nov 2002, Derick Rethans wrote:
> On Mon, 18 Nov 2002, Marcus Börger wrote:
>
> > Brian could you create a short test for the segfault? It would help us
> > finding out the problems.
>
> For now I think it's very wise to remove all the e*() memory functions
> from the branch, it's no
On Mon, 18 Nov 2002, Marcus Börger wrote:
> Brian could you create a short test for the segfault? It would help us
> finding out the problems.
For now I think it's very wise to remove all the e*() memory functions
from the branch, it's not strictly needed and we need to be very careful
not to e
At 13:07 18.11.2002, Derick Rethans wrote:
On Mon, 18 Nov 2002, Brian Havard wrote:
> Derick Rethans wrote:
> > On Sun, 17 Nov 2002, Derick Rethans wrote:
> >
> >
> >>On Sun, 17 Nov 2002, Brian Havard wrote:
> >>
> >>
> >>>When trying out the RC1 code I found that my GD test segfaults every
time
On Mon, 18 Nov 2002, Brian Havard wrote:
> Derick Rethans wrote:
> > On Sun, 17 Nov 2002, Derick Rethans wrote:
> >
> >
> >>On Sun, 17 Nov 2002, Brian Havard wrote:
> >>
> >>
> >>>When trying out the RC1 code I found that my GD test segfaults every time. I
> >>>traced the problem to the fact th
Derick Rethans wrote:
On Sun, 17 Nov 2002, Derick Rethans wrote:
On Sun, 17 Nov 2002, Brian Havard wrote:
When trying out the RC1 code I found that my GD test segfaults every time. I
traced the problem to the fact that efree is used on memory that was
allocated with strdup. See the fontlis
On Sun, 17 Nov 2002, Derick Rethans wrote:
> On Sun, 17 Nov 2002, Brian Havard wrote:
>
> > When trying out the RC1 code I found that my GD test segfaults every time. I
> > traced the problem to the fact that efree is used on memory that was
> > allocated with strdup. See the fontlist variable
On Sun, 17 Nov 2002, Brian Havard wrote:
> When trying out the RC1 code I found that my GD test segfaults every time. I
> traced the problem to the fact that efree is used on memory that was
> allocated with strdup. See the fontlist variable in
> ext\gd\libgd\gdft.c:fontFetch()
>
> This starte
When trying out the RC1 code I found that my GD test segfaults every time. I
traced the problem to the fact that efree is used on memory that was
allocated with strdup. See the fontlist variable in
ext\gd\libgd\gdft.c:fontFetch()
This started happening when gdhelpers.c was changed to use emallo
10 matches
Mail list logo