Opened 20 years ago
Closed 20 years ago
#838 closed defect (fixed)
uninitialized geotransformObj gt
Reported by: | Owned by: | warmerdam | |
---|---|---|---|
Priority: | high | Milestone: | |
Component: | MapServer C Library | Version: | 4.3 |
Severity: | minor | Keywords: | |
Cc: |
Description
I'm using valgrind today and am seeing a lot of these errors/warnings ==5228== Conditional jump or move depends on uninitialised value(s) ==5228== at 0x1C023E9E: msProjectPoint (mapproject.c:97) ==5228== by 0x1C024075: msProjectGrowRect (mapproject.c:125) ==5228== by 0x1C02448A: msProjectRect (mapproject.c:175) ==5228== by 0x1C037506: msDrawVectorLayer (mapdraw.c:731) ==5228== by 0x1C037244: msDrawLayer (mapdraw.c:627) ==5228== by 0x1C03698A: msDrawMap (mapdraw.c:322) ==5228== by 0x1BFCE27E: mapObj_draw (mapscript_wrap.c:1438) ==5228== by 0x1BFED354: _wrap_mapObj_draw (mapscript_wrap.c:16905) ==5228== by 0x80EA40C: PyCFunction_Call (in /usr/bin/python) ==5228== by 0x805B3B6: PyObject_Call (in /usr/bin/python) ==5228== by 0x80AB92A: (within /usr/bin/python) ==5228== by 0x80A93C7: (within /usr/bin/python) Checked into mapfile.c and it looks like the gt members of projections are not being initialized in msInitProjection.
Change History (3)
comment:2 by , 20 years ago
Thanks, Frank. I mighta tried to fix this myself but I don't know my way around the geotransform stuff at all. All the warnings about conditional jumps are gone from the single test I am running.
Note:
See TracTickets
for help on using tickets.