Justin Pryzby <[EMAIL PROTECTED]> writes:
>> > I note that there's still a number of valgrind warnings :/
>>
>> Mostly harmless as far as I can tell, but patches are always welcome. ;)
>
> What leads you to believe that they are harmless? Sorry, just trying
> to learn something (else) :)
All th
On Thu, Mar 09, 2006 at 11:19:38AM +0100, Matej Vela wrote:
> Justin Pryzby <[EMAIL PROTECTED]> writes:
>
> > On Tue, Mar 07, 2006 at 11:47:25PM +0100, Matej Vela wrote:
> >> I think I've tracked this down to a memory overrun in src/X11dev.c.
> >> Does the attached patch work for you?
> >
> > That
Justin Pryzby <[EMAIL PROTECTED]> writes:
> On Tue, Mar 07, 2006 at 11:47:25PM +0100, Matej Vela wrote:
>> I think I've tracked this down to a memory overrun in src/X11dev.c.
>> Does the attached patch work for you?
>
> That's awesome :) How did you find it?
I set a bunch of breakpoints to see w
On Tue, Mar 07, 2006 at 11:47:25PM +0100, Matej Vela wrote:
> tag 152128 patch
> thanks
>
> Helge Kreutzmann <[EMAIL PROTECTED]> writes:
>
> > Trying to open a vcg file causes a segfault. [...]
>
> I think I've tracked this down to a memory overrun in src/X11dev.c.
> Does the attached patch work
tag 152128 patch
thanks
Helge Kreutzmann <[EMAIL PROTECTED]> writes:
> Trying to open a vcg file causes a segfault. [...]
I think I've tracked this down to a memory overrun in src/X11dev.c.
Does the attached patch work for you?
Thanks,
Matej
--- vcg-1.30debian.orig/src/X11dev.c
+++ vcg-1.30deb
5 matches
Mail list logo