HTTrack Website Copier
Free software offline browser - FORUM
Subject: Problems with memory in c++
Author: MBM
Date: 03/13/2004 14:56
 
I write part of the valdgrind message when I execute my
program. I don't understand anything. What can I do? 

==1166== Use of uninitialised value of size 8
==1166==    at 0x8060D1C:
OperIteracion::hallarPrototipoNoVaso(perfil *, int)
(OperIteracion.cpp:43)
==1166==    by 0x8060F37:
OperIteracion::hallarContraste(perfil *, int)
(OperIteracion.cpp:75)
==1166==    by 0x806549C: Tracking::guardarPerfil(Perfil *)
(Tracking.cpp:182)
==1166==    by 0x80667B4: Tracking::separarPerfil(Perfil *,
int, Perfil *, Perfil *) (Tracking.cpp:351)
==1166==
==1166== Conditional jump or move depends on uninitialised
value(s)
==1166==    at 0x8064583: Tracking::Tracking(Image *, p, p,
int, double) (Tracking.cpp:17)
==1166==    by 0x8065596: Tracking::guardarPerfil(Perfil *)
(Tracking.cpp:187)
==1166==    by 0x80667B4: Tracking::separarPerfil(Perfil *,
int, Perfil *, Perfil *) (Tracking.cpp:351)
==1166==    by 0x80671F4: Tracking::hallarPerfil(Image *, p,
Perfil *, int, int) (Tracking.cpp:478)

On the other hand, if I use gdb, I receive the following error:

Program received signal SIGSEGV, Segmentation fault.
0x400fcbf3 in mallopt () from /lib/libc.so.6
(gdb) 

I hope your help. Thanks! 
 
Reply


All articles

Subject Author Date
Problems with memory in c++

03/13/2004 14:56




4

Created with FORUM 2.0.11