[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Bugs in fillHole ?
From: |
Manuel Guesdon |
Subject: |
Bugs in fillHole ? |
Date: |
Mon, 17 Feb 2003 13:41:45 +0100 (CET) |
Hi,
I've tried valgrind to find memory problems and found problems in GSSTring.m
fillHole.
==20804== Invalid read of size 1
==20804== at 0x40CD337A: fillHole (GSString.m:1065)
==20804== by 0x40CCDFF1: _i_GSMutableString__deleteCharactersInRange_
(GSString.m:2700)
==20804== by 0x40573359:
_i_GSWDynamicURLString_GSWDynamicURLStringParsing__compose
(GSWDynamicURLString.m:328)
==20804== by 0x405730A6: _i_GSWDynamicURLString__description
(GSWDynamicURLString.m:292)
I get it when
self->_count=75, index=0, size=75 self->_flags.wide=0
but I don't understand why :-(
I've looked also at STABLE_MEMCPY code and I think memcpy src and dst
arguments
are inversed. Aren't they ?
Manuel
--
______________________________________________________________________
Manuel Guesdon - ORANGE CONCEPT <mguesdon@orange-concept.com>
14 rue Jean-Baptiste Clement - 93200 Saint-Denis - France
Tel: +33 1 4940 0997 - Fax: +33 1 4940 0998
- Bugs in fillHole ?,
Manuel Guesdon <=